THREE.JS / FOUNDATIONS 305
Recover the renderer.
A renderer is not an application state machine. Exercise a real WebGL context loss, observe the restore boundary, then rebuild from a small CPU-owned scene recipe when the backend needs a fresh instance.
Preparing the renderer and recovery fixture…
failure boundary
Own the recovery policy.
Only the direct WebGL2 lane claims a real loss/restore. WebGPU callbacks and policy actions are labeled observations or synthetic application tests.
stateBOOT
backend—
renderer0
frames0
losses0
rebuilds0
resource manifest / renderer.info.memory
- manifest
- —
- geometry
- —
- textures
- —
- sample
- NOT RUN
01listen for the backend event
02quiesce rendering during loss
03rehydrate from CPU recipe
event timeline
- waiting for initialization
Renderer resilience error
The renderer could not start.
Drag to orbit · R resets · loss/restore is supported only in the direct WebGL2 lane
LAB 305 / RENDERER RESILIENCE