# THREE.WebGLRenderer

**URL:** <https://discourse.threejs.org/t/three-webglrenderer/64730>\
**Category:** Questions\
**Created:** [April 28, 2024, 12:04pm UTC](https://discourse.threejs.org/t/three-webglrenderer/64730 "2024-04-28T12:04:20Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alaa\_Ezat](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/alaa_ezat/32/36895_2.png) [@Alaa\_Ezat](https://discourse.threejs.org/u/Alaa_Ezat)\
**Post date:** [April 28, 2024, 12:04pm UTC](https://discourse.threejs.org/t/three-webglrenderer/64730/1 "2024-04-28T12:04:20Z")

</div>

THREE.WebGLRenderer: Context Lost.  
this message appears when user moving between pages how to solve this ?

---

<div class="post-metadata">

**Author:** ![mjurczyk](https://yyz1.discourse-cdn.com/flex035/user_avatar/discourse.threejs.org/mjurczyk/32/10995_2.png) [@mjurczyk](https://discourse.threejs.org/u/mjurczyk)\
**Post date:** [April 28, 2024, 12:16pm UTC](https://discourse.threejs.org/t/three-webglrenderer/64730/2 "2024-04-28T12:16:59Z")

</div>

I’m assuming you’re using something react-three-fiberish / SPA / next.js, in which case you can safely ignore it - its marked as an error but it’s harmless - it’s happening since the canvas was already removed from DOM but one more animation frame was already scheduled.

If you manage your own animation loop - without r3f- just make sure to either not dispose three.js canvas at any point, or stop the rendering loop before disposing the canvas DOM element.