What is not recorded

A Trace never guesses. When it keeps less than the whole of a value, or stops recording early, it says so on the Timeline bar.

What a Trace leaves out

Point at the (i) button on the Timeline bar to see What’s not recorded:

• Objects are recorded 8 levels deep and 512 entries wide, and strings up to 1,024 characters. Past that, a value says (not shown — too deep) or (not shown — too wide).
• What the console prints goes less deep, but keeps longer strings.
• Getters and setters are not called, so recording never runs your code. They show as (getter), (setter) or (getter and setter).
• An object shows what it held at each Step, not what it holds at the end.
• If something could have changed an object without JSpark seeing it, the box adds: Something may have changed an object when we weren’t looking.

Only Node Snippets are recorded. A Snippet that runs in a web page has no Timeline.

When a Trace is cut short

A Trace stops recording at the first of three limits. The Steps it recorded still work: you can move through them, and read their values, as usual.

At the step or memory limit, only the recording stops: the Run goes on to its end, and the console has all its output. Point at the chip to see which limit it was.

Record more Steps JSpark+

JSpark+ records up to 200,000 Steps at first. Click incomplete — record more to record again with four times as many Steps as this recording has. Click it again on the new recording to go further, up to 2,000,000 Steps.

In JSpark, a recording holds 5,000 Steps. At that limit, clicking incomplete — record more says: JSpark+ records up to 2,000,000 Steps. JSpark records 5,000. Inside lines fills the limit sooner: see Step Detail.