@expofp/renderer 3.42.1 → 3.43.0

package/dist/Renderer.js

@@ -1,5 +1,5 @@
 import { jsx as _jsx, jsxs as _jsxs } from "react/jsx-runtime";
-import { StrictMode, Suspense } from 'react';
+import { StrictMode, Suspense, useEffect, useRef, } from 'react';
 import { Controls } from './controls';
 import { CanvasWithDebug, DebugOverlay } from './debug';
 import { PointerMissed } from './events/PointerMissed';
@@ -27,6 +27,27 @@ export function Renderer(props) {
     const { debug, scene, memoryLimit, minZoom, maxZoom, minPitch, maxPitch, bounds, smoothTime, controls, lighting, visibleRect, onPointerMissed, gl, requestFrame, onFrame, children, ...canvasProps } = props;
     const cameraProps = { minZoom, maxZoom, minPitch, maxPitch, bounds, smoothTime };
     const external = gl !== undefined;
+    // The context this mount created, released here rather than left to R3F. `<Canvas>`'s teardown
+    // (`unmountComponentAtNode`) defers `forceContextLoss()` behind a 500 ms `setTimeout`, inside a
+    // `try` that disconnects events first — so a host that unmounts the renderer holds a full
+    // viewport of GPU memory for half a second after it thought the surface was gone, and holds it
+    // forever if anything ahead of the loss in that block throws. An SDK `destroy()` that returns
+    // while the plan still owns a WebGL2 context is the same bug on a timer, and a plan swap pays it
+    // as a real transient: the incoming plan's context is created while the outgoing one still
+    // holds its own. R3F's deferred pass still runs afterwards and is unharmed — its remaining work
+    // (`renderLists.dispose()`, `dispose(scene)`) is no-ops on a lost context.
+    //
+    // Safe as a plain unmount effect only because `<StrictMode>` starts *below* here, wrapping the
+    // canvas rather than this component: nothing simulates a remount at this level, so the cleanup
+    // runs when the renderer is actually going away. External mode never fills the ref — the host
+    // owns that context, and `ExternalCanvas` neuters `forceContextLoss` for the same reason.
+    const rendererRef = useRef(undefined);
+    useEffect(() => {
+        return () => {
+            rendererRef.current?.forceContextLoss();
+            rendererRef.current = undefined;
+        };
+    }, []);
     // The one tree, whichever canvas it lands on. The mount decides nothing about it; the tree
     // leaves out what external mode has no object for — the controls here, the camera inside Scene.
     const tree = (_jsx(DebugOverlay, { enabled: debug, children: _jsxs(Scene, { sceneDef: scene, external: external, memoryLimit: memoryLimit, lighting: lighting, visibleRect: visibleRect, ...cameraProps, children: [!external && _jsx(Controls, { config: controls }), _jsx(PointerMissed, { onPointerMissed: onPointerMissed }), children] }) }));
@@ -59,7 +80,11 @@ export function Renderer(props) {
                 // a compile synchronous: 17 programs cost 64 ms of main thread on a large scene, in
                 // blocks of up to 12 ms, and they land in the frames where the layers are still mounting.
                 // Debug keeps the check, because a broken shader has to report itself somewhere.
+                //
+                // The root state is also this mount's one handle on the renderer, which the unmount
+                // effect above needs to release its context.
                 onCreated: (state) => {
                     state.gl.debug.checkShaderErrors = debug ?? false;
+                    rendererRef.current = state.gl;
                 }, frameloop: debug ? 'always' : 'demand', resize: { debounce: 50 }, children: tree }) }) }));
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@expofp/renderer",
-  "version": "3.42.1",
+  "version": "3.43.0",
   "repository": {
     "type": "git",
     "url": "https://github.com/expofp/efp-app.git",
@@ -42,7 +42,7 @@
     "troika-three-text": "^0.52.5",
     "tslib": "^2.3.0",
     "webgl-memory": "^1.1.3",
-    "@expofp/geometry": "3.42.1"
+    "@expofp/geometry": "3.43.0"
   },
   "devDependencies": {
     "@react-three/test-renderer": "^9.1.0",