Browser & Frontend Runtime

V8 internals: free-recall review

Crux Free-recall prompts across the V8 unit. Answer each in your own words first — hidden classes, IC states, JIT tiers, deopt-loops, Orinoco — then reveal the model answer and compare.

Your altitude — climbing toward senior

ZeroJuniorMiddleSenior

You are at senior altitude — in orbit

◷ 14 min

Retrieval beats re-reading. For each prompt, reconstruct a full answer from memory before you open the model answer — the effort of recall is what fixes the V8 mental model in place.

Goal

Reconstruct the unit’s core mechanisms — hidden-class transitions, the IC state machine, the four-tier pipeline, the deopt-loop, and Orinoco’s barriers — without looking back at the lessons.

Recall before you leave

01
What is a hidden class, and why does property-addition ORDER decide whether two objects share one?
02
Describe the IC state machine and what triggers each transition.
03
Name V8's four JIT tiers in order and the niche each fills.
04
What distinguishes a one-time deopt from a deopt-loop, and why is the loop catastrophic?
05
How does Orinoco split GC work, and why does concurrent marking need a write barrier?
06
Why do TypedArrays bypass the IC layer, and when is that the right tool?

Recap

If you could reconstruct each answer from memory, you hold the unit’s spine: property-addition order sets the hidden class, the hidden class drives the IC state machine, the FeedbackVector and type stability govern how far up the four-tier ladder a function climbs (and whether it falls into a deopt-loop), Orinoco’s barriers keep concurrent collection correct, and TypedArrays sidestep the IC and GC layers entirely. Every fix in the unit lives upstream of V8, in the shape and the numeric type of your data.

Continue the climb ↑V8 internals: code and trace reading