- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
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
- Etiquetas:
- Memory leak
- opengl
- shared context
Enlace copiado
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
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
- Marcar como nuevo
- Favorito
- Suscribir
- Silenciar
- Suscribirse a un feed RSS
- Resaltar
- Imprimir
- Informe de contenido inapropiado
+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

- Suscribirse a un feed RSS
- Marcar tema como nuevo
- Marcar tema como leído
- Flotar este Tema para el usuario actual
- Favorito
- Suscribir
- Página de impresión sencilla