Analyzers
Support for Analyzers (Intel VTune™ Profiler, Intel Advisor, Intel Inspector)
Announcements
This community is designed for sharing of public information. Please do not share Intel or third-party confidential information here.

OPENGL memory leaks

Peter_S_8
Beginner
159 Views

Hello from germany

I have just started with the Intel Inspector and wonder why it throws a lot of memory leak messages referring

to functios as wglCreateContext - wglMakeCurrent and so on.

All these handle were released at program exit, with error checking and everything looks fine.

Additionally it creates the same error multiple times - shows the same line of code..

I would be happy for any explaation or solution

kind regards

 Peter

0 Kudos
4 Replies
SergeyKostrov
Valued Contributor II
159 Views
If your code does something like the following example: ... HDC hdc = NULL; HGLRC hglrc = NULL; hglrc = wglCreateContext( hdc ); ... // Processing with OpenGL API functions ... wglDeleteContext( hglrc ); ... then you could simply ignore that Inspector XE message.
Holly_W_Intel
Employee
159 Views

Sergey is correct that if your actual code is safe (which his example is) you can just go ahead and ignore the messages or set up a suppression to automatically remove them.

 

We are currently in the process of doing some work to improve our handling of memory deallocated at_exit(). If you would like to be informed when we have an update and give us feedback on how it works for you, please send me an email. (holly.l.wilper@intel.com)

SergeyKostrov
Valued Contributor II
159 Views
Hi Holly, >>...We are currently in the process of doing some work to improve our handling of memory deallocated at_exit()... It would be nice to learn more about that new technique. Thanks in advance.
Holly_W_Intel
Employee
159 Views

Unfortunately I don't have that many details that I can give you, right now. I'll stick a mental pin in this topic to update it when there is more I can say. (sorry).

Reply