- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
The way to reproduce this memory leak is to create a shared context, then create some textures on that shared context (should be more than one texture), then change to the main OpenGL context and destroy the previously created textures. If you do this process in a loop, you will see that the GPU memory grows very fast.
I've done a simple program in github that reproduce this, so you can try and reproduce: https://github.com/yosoymin/InitGL/tree/intel_shared_context_leak
This program runs ok in older versions of Intel drivers (27.20.100.8681 tested in a Intel HD 655 and HD 630) and aslo in Linux or with other vendor drivers.
More info here: https://community.intel.com/t5/Graphics/OpenGL-Windows-drivers-for-Intel-HD-630-leaking-GPU-memory-when/td-p/1274423
Thanks
Link Copied
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
yosoymin, Thank you for posting in the Intel® Communities Support.
Please keep checking your original thread for further assistance and possible updates on this matter:
Regards,
Albert R.
Intel Customer Support Technician
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
+Following, I have a similar issue with Intel HD 630
https://community.intel.com/t5/Graphics/Debugging-issues-with-Intel-UHD-630-620-drivers/m-p/1282808#M97214

- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page