# Memory Leak in Screenshots **URL:** \ **Category:** Bugs\ **Created:** [January 7, 2023, 5:49pm UTC](https://forum.babylonjs.com/t/memory-leak-in-screenshots/37178 "2023-01-07T17:49:37Z")\ **Posts on this page:** 1\ **Showing post:** 19
**Author:** ![Evgeni\_Popov](https://sea2.discourse-cdn.com/flex024/user_avatar/forum.babylonjs.com/evgeni_popov/32/4432_2.png) [@Evgeni\_Popov](https://forum.babylonjs.com/u/Evgeni_Popov)\ **Post date:** [January 10, 2023, 8:41pm UTC](https://forum.babylonjs.com/t/memory-leak-in-screenshots/37178/19 "2023-01-10T20:41:35Z")
That means any texture created is leaking, disposing of it does not reclaim the GPU memory… It sounds like a bug of the driver to me, which does not reclaim GPU memory properly. It is more apparent now with our new screenshot code because we are creating a new texture each time, but to me the problem is not with our code. cc @sebavan in case it rings some bells for him. Note that if that helps, you can keep the overriden method of `BABYLON.DumpTools.DumpData` I provided in the PG above if the screenshots are ok with you with this method. Our new implementation takes care of the pre-multiply setting of canvas that made data with alpha channel not having the proper look, but screenshots don’t have an alpha channel so that should be fine. And thanks for your patience with the testings! --- _[View the full topic](https://forum.babylonjs.com/t/memory-leak-in-screenshots/37178)._