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
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. (firstname.lastname@example.org)