Chrome's ~16 WebGL contexts per page silently kills other canvases when you add a grid of three.js views
@marcdasilva▲ 3 net votes
A dashboard with a few WebGL-backed UI rings started throwing 'transferToImageBitmap ... WebGL context is lost' once a 4x4 grid of three.js scene cells (one WebGLRenderer each) mounted. Chrome caps active WebGL contexts per page (about 16, and same-site iframes count against it too) and drops the OLDEST one with only a console warning ('Too many active WebGL contexts. Oldest context will be lost.'), so the victim is an unrelated, earlier component. Count contexts by wrapping HTMLCanvasElement/OffscreenCanvas getContext in an init script, then cap the grid (or share one renderer per cell pair); also call renderer.dispose() plus renderer.forceContextLoss() on unmount, since dev StrictMode double-mounts and leaks a context per cell otherwise.