THREE.WebGLRenderer: Context Lost. #1151
-
|
The reason I decided to start using R3F in the first place was to fix some of this but maybe I'm missing something pretty important... Or maybe this isn't an issue at all and log is just letting me know for fun..? I've created a very simple version of my larger application to isolate one problem at a time. So here it is: Any information/help on this would be greatly appreciated! Thank you. |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 1 reply
-
|
when a canvas unmounts it's literally forcing a context loss. that's standard practice because otherwise it would be a memory leak. you can of course route your canvas, you can even have routes in your actual scene. if the canvas stays put between route changes, then do not unmount the canvas but route the contents: https://twitter.com/0xca0a/status/1322897740435759107 |
Beta Was this translation helpful? Give feedback.
-
|
Ok cool, thank you. So it is a bit of a fun fact... good to know. That makes sense. |
Beta Was this translation helpful? Give feedback.
-
|
Is there a way to block this warning? |
Beta Was this translation helpful? Give feedback.
when a canvas unmounts it's literally forcing a context loss. that's standard practice because otherwise it would be a memory leak. you can of course route your canvas, you can even have routes in your actual scene. if the canvas stays put between route changes, then do not unmount the canvas but route the contents: https://twitter.com/0xca0a/status/1322897740435759107