A failed P5LIVE compile leaves the last good frame visible rather than blanking the canvas

P5LIVE recompiles on every save or keypress. When a soft or hard compile fails — syntax error, runtime error, or bad paste — the new broken code is never installed; the browser keeps showing the previously rendered frame. ‘Is it broken?’ therefore requires both reading the error line and looking at the canvas: a frozen frame may be a valid static sketch or may be stuck on the last good render after a failed update. Recovery is always: fix the code and re-save. A syntax error alone never silences or blanks the sketch.

Examples

Type elipse(...) (misspelled) and save — the canvas keeps showing the previous frame. Fix to ellipse(...) and save — the canvas updates.

Assessment

A student edits a P5LIVE sketch and the canvas does not change. Name two distinct reasons this could happen and explain how to determine which one applies.