# OpenGL Posssible memory leak in OpenGL Intel Win7 drivers

## Recommended Posts

int *ptr, MSVC 2008, debug build, value of 0x0018f668.

Just because it works on one person's machine using a specific compiler does not make it globally valid. The C/C++ standard is quite explicit that uniitalized pointers are undefined. That means that the compiler is largely free to do whatever it wants with them; it may give a value of 0, it may set to random garbage, and that random garbage may or may not point to somewhere valid in memory.

If you're in the habit of doing this, and of relying on it, please remind me to never use any software you write.

##### Share on other sites
[quote name='mhagain' timestamp='1329263308' post='4913186']
If you're in the habit of doing this, and of relying on it, please remind me to never use any software you write.
[/quote]

I always clean up any warning the compiler gives, and this includes uninitialized variables. So that kind of thing isn't going to happen ever in software I write.

##### Share on other sites
But you define all your pointer variables global, not local?

##### Share on other sites
[quote name='Martins Mozeiko' timestamp='1329268804' post='4913202']
But you define all your pointer variables global, not local?
[/quote]

why did you think that? I just wanted to show you a case where an uninitialized pointer actually is initialized. That was all.
I didn't imply that I use only global variables...

##### Share on other sites
[b] [url="../../user/195648-mshafey/"]@mshafey[/url][/b]

gDEBugger has some nice memory leak tracking features, you should check it out

##### Share on other sites
[quote name='Yours3!f' timestamp='1329270258' post='4913209']why did you think that? I just wanted to show you a case where an uninitialized pointer actually is initialized. That was all.
I didn't imply that I use only global variables...
[/quote]
Previously you said, I'm quoting: "and pointer declaration depends on the compiler (but you are right it should be undefined)". But Now you say they are initialized...

How can "uninitialized pointer" be actually "initialized". There is no such thing as global unitialized variable from users point of view. C standard requires all global variables to be initialized to 0 or by calling C++ constructor.

##### Share on other sites
[quote name='mhagain' timestamp='1329248389' post='4913090']
[quote name='mshafey' timestamp='1329247414' post='4913082']
Thanks for the suggestion. I've tried your code, it works, but it doesn't fix the leak. I'm still seeing memory leaking at the same rate on the affected platforms.
[/quote]
That's interesting. Let's try to pin down which call is causing it. What happens if you comment out the glTexSubImage2D call? And if you comment out the glMapBuffer block (but leave glTexSubImage2D in and coming from the PBO)?
[/quote]

gDEBugger with the code I posted in the first post. Upon application exit it says [b]"Checking for memory leaks - Context 1 deleted. Memory Leak: 2 object(s) are leaked in GL Context 1 [Leak Size: 2,400KB]"[/b]. Here are Process Explorer graphs for the original code running for a few minutes.

GPU graph: [url="http://i.imgur.com/KgXix.png"]http://i.imgur.com/KgXix.png[/url]
Performance graph: [url="http://i.imgur.com/bD9RH.png"]http://i.imgur.com/bD9RH.png[/url]

I took out glMapBuffer()/glUnmapBuffer() block. Leak persists. Same for the glTexSubImage2D() call. Took them both out and still. Which lead me to remove everything except just basic calls to draw a rectangle switching colors. I'm sorry I sent everyone in the wrong direction here. It seems like even the most basic GL code causes Windows 7 machines to leak memory. I trimmed it down to this and it still leaks.

[code]

void paintGL();
void timerCallback(int value);
void changeSize(int w, int h);

unsigned char c = 255;

int main(int argc, char **argv)
{
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_DEPTH | GLUT_DOUBLE | GLUT_RGBA);
glutInitWindowPosition(300, 300);
glutInitWindowSize(640, 480);
int windowHandle = glutCreateWindow("Window");
glutDisplayFunc(paintGL);
glutReshapeFunc(changeSize);
timerCallback(0);
glutMainLoop();
glutDestroyWindow(windowHandle);
return 0;
}

void paintGL()
{
c = c? 0 : 255;
glColor3ub(c, c, c);
{
glVertex3f(-1, 1, 0);
glVertex3f(1, 1, 0);
glVertex3f(1, -1, 0);
glVertex3f(-1, -1, 0);
}
glEnd();

glutSwapBuffers();
}

void changeSize(int w, int h)
{
glViewport(0, 0, w, h);
}

void timerCallback(int value)
{
glutPostRedisplay();
glutTimerFunc(5, timerCallback, 0);
}

[/code]

I might add that in some runs, this code starts off at about 18 MB and goes up to and then stabilizes at 40 MB in a 5-6 minutes.

##### Share on other sites
Hi.

Could it be an issue with GLUT ?

This part :
[code]void timerCallback(int value)
{
glutPostRedisplay();
glutTimerFunc(5, timerCallback, 0);
}[/code]

Shouldn't be :
[code]
int main(int argc, char **argv)
{
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_DEPTH | GLUT_DOUBLE | GLUT_RGBA);
glutInitWindowPosition(300, 300);
glutInitWindowSize(640, 480);
int windowHandle = glutCreateWindow("Window");
glutDisplayFunc(paintGL);
glutReshapeFunc(changeSize);
glutTimerFunc(5, timerCallback, 0);
glutMainLoop();
glutDestroyWindow(windowHandle);
return 0;
}

void timerCallback(int value)
{
glutPostRedisplay();
}[/code]

? Edited by vNeeki

##### Share on other sites
No. I'm finding the same behavior with QGLWidget (not using GLUT). Also, VLC with OpenGL output seems to have this memory increase problem as well.

##### Share on other sites
[quote name='mshafey' timestamp='1329322541' post='4913374']
[quote name='mhagain' timestamp='1329248389' post='4913090']
[quote name='mshafey' timestamp='1329247414' post='4913082']
Thanks for the suggestion. I've tried your code, it works, but it doesn't fix the leak. I'm still seeing memory leaking at the same rate on the affected platforms.
[/quote]
That's interesting. Let's try to pin down which call is causing it. What happens if you comment out the glTexSubImage2D call? And if you comment out the glMapBuffer block (but leave glTexSubImage2D in and coming from the PBO)?
[/quote]

gDEBugger with the code I posted in the first post. Upon application exit it says [b]"Checking for memory leaks - Context 1 deleted. Memory Leak: 2 object(s) are leaked in GL Context 1 [Leak Size: 2,400KB]"[/b]. Here are Process Explorer graphs for the original code running for a few minutes.

GPU graph: [url="http://i.imgur.com/KgXix.png"]http://i.imgur.com/KgXix.png[/url]
Performance graph: [url="http://i.imgur.com/bD9RH.png"]http://i.imgur.com/bD9RH.png[/url]

I took out glMapBuffer()/glUnmapBuffer() block. Leak persists. Same for the glTexSubImage2D() call. Took them both out and still. Which lead me to remove everything except just basic calls to draw a rectangle switching colors. I'm sorry I sent everyone in the wrong direction here. It seems like even the most basic GL code causes Windows 7 machines to leak memory. I trimmed it down to this and it still leaks.

[code]

void paintGL();
void timerCallback(int value);
void changeSize(int w, int h);

unsigned char c = 255;

int main(int argc, char **argv)
{
glutInit(&argc, argv);
glutInitDisplayMode(GLUT_DEPTH | GLUT_DOUBLE | GLUT_RGBA);
glutInitWindowPosition(300, 300);
glutInitWindowSize(640, 480);
int windowHandle = glutCreateWindow("Window");
glutDisplayFunc(paintGL);
glutReshapeFunc(changeSize);
timerCallback(0);
glutMainLoop();
glutDestroyWindow(windowHandle);
return 0;
}

void paintGL()
{
c = c? 0 : 255;
glColor3ub(c, c, c);
{
glVertex3f(-1, 1, 0);
glVertex3f(1, 1, 0);
glVertex3f(1, -1, 0);
glVertex3f(-1, -1, 0);
}
glEnd();

glutSwapBuffers();
}

void changeSize(int w, int h)
{
glViewport(0, 0, w, h);
}

void timerCallback(int value)
{
glutPostRedisplay();
glutTimerFunc(5, timerCallback, 0);
}

[/code]

I might add that in some runs, this code starts off at about 18 MB and goes up to and then stabilizes at 40 MB in a 5-6 minutes.
[/quote]

This is crazy... I can't believe Intel drivers are this bad on windows... Well I ran into similar problems on windows when I worked for a company for the last summer, and eventually I had to switch to DirectX because the OGL functions just didn't work as expected (or caused crashes etc.)

##### Share on other sites
On reconsidering this, memory usage starting low, followed by an increase then stabilize is probably nothing to be worried about. It's where the stabilize part doesn't happen that you need to start worrying (that's a real leak - stabilization isn't a leak, it's just using resources). What's actually happening would be internal driver behaviour so we're reduced to guessing here, but going by your final stripped down program a reasonable and plausable guess would be that the driver is buffering up geometry used by immediate mode calls - it may for example be writing them into a dynamic VBO and then issuing real draw calls behind the scenes from that.

As for the two leaked objects - I have a suspicion which a simple test will help confirm. If you totally strip down the program so that each frame is nothing more than a clear and swapbuffers, and if they still leak, then I'm going to suggest that they might be your backbuffer and depth buffer (these do exist as actual GPU objects although OpenGL doesn't really expose them as such) - 640 * 480 * 4 * 2 is very close to the reported leak size of 2.4 mb (if my other guess is correct then the increase/stabilize usage pattern should also go away with this strip down). Of course, if gDEBugger allows you to drill further into this and identify which objects were leaked then it would be additional useful info.

##### Share on other sites
[quote name='mhagain' timestamp='1329344027' post='4913484']
On reconsidering this, memory usage starting low, followed by an increase then stabilize is probably nothing to be worried about. It's where the stabilize part doesn't happen that you need to start worrying (that's a real leak - stabilization isn't a leak, it's just using resources). What's actually happening would be internal driver behaviour so we're reduced to guessing here, but going by your final stripped down program a reasonable and plausable guess would be that the driver is buffering up geometry used by immediate mode calls - it may for example be writing them into a dynamic VBO and then issuing real draw calls behind the scenes from that.
[/quote]

Thanks. We realized this is true. From [url="http://www.opengl.org/wiki/FAQ#Memory_Usage"]here[/url]:

[quote]
[b] Memory Usage[/b]

[color=#000000][font=sans-serif][size=3]It seems to be common to think that there is a memory leak in the OpenGL driver. Some users write simple programs such as this[/size][/font][/color]

[color=#000000][font=sans-serif][size=3] glClear[color=#008000]([/color]...[color=#008000])[/color][color=#008080];[/color]
SwapBuffers[color=#008000]([/color]...[color=#008000])[/color][color=#008080];[/color][/size][/font][/color]
[color=#000000][font=sans-serif][size=3]and they observe that their memory usage goes up each time their Display function is called. That is normal. The driver might allocate some memory space and since the driver is basically a black box, we don't know what it is doing. The driver might be doing some work at optimizing in a secondary thread or preparing some buffering area. We don't know what it is doing, but there is no memory leak.[/size][/font][/color][/quote]

The problem is, in our application we're dealing with many OpenGL contexts at once (up to 30). For Windows XP on the same hardware, OpenGL memory is small compared to Windows 7. So in a day my application memory goes up to 1.5 GB on Win 7, but stays at 500 MB on XP.

We'll either require more memory or reduce the number of contexts used.

Thanks for the useful input everyone.

## Create an account or sign in to comment

You need to be a member in order to leave a comment

## Create an account

Sign up for a new account in our community. It's easy!

Register a new account

• ## Partner Spotlight

• ### Forum Statistics

• Total Topics
627682
• Total Posts
2978613
• ### Similar Content

• Both functions are available since 3.0, and I'm currently using glMapBuffer(), which works fine.
But, I was wondering if anyone has experienced advantage in using glMapBufferRange(), which allows to specify the range of the mapped buffer. Could this be only a safety measure or does it improve performance?
Note: I'm not asking about glBufferSubData()/glBufferData. Those two are irrelevant in this case.
• By xhcao
Before using void glBindImageTexture(    GLuint unit, GLuint texture, GLint level, GLboolean layered, GLint layer, GLenum access, GLenum format), does need to make sure that texture is completeness.
• By cebugdev
hi guys,
are there any books, link online or any other resources that discusses on how to build special effects such as magic, lightning, etc. in OpenGL? i mean, yeah most of them are using particles but im looking for resources specifically on how to manipulate the particles to look like an effect that can be use for games,. i did fire particle before, and I want to learn how to do the other 'magic' as well.
Like are there one book or link(cant find in google) that atleast featured how to make different particle effects in OpenGL (or DirectX)? If there is no one stop shop for it, maybe ill just look for some tips on how to make a particle engine that is flexible enough to enable me to design different effects/magic
let me know if you guys have recommendations.
Thank you in advance!
• By dud3
How do we rotate the camera around x axis 360 degrees, without having the strange effect as in my video below?
Mine behaves exactly the same way spherical coordinates would, I'm using euler angles.
Tried googling, but couldn't find a proper answer, guessing I don't know what exactly to google for, googled 'rotate 360 around x axis', got no proper answers.

References:
Code: https://pastebin.com/Hcshj3FQ
The video shows the difference between blender and my rotation:

• By Defend
I've had a Google around for this but haven't yet found some solid advice. There is a lot of "it depends", but I'm not sure on what.
My question is what's a good rule of thumb to follow when it comes to creating/using VBOs & VAOs? As in, when should I use multiple or when should I not? My understanding so far is that if I need a new VBO, then I need a new VAO. So when it comes to rendering multiple objects I can either:
* make lots of VAO/VBO pairs and flip through them to render different objects, or
* make one big VBO and jump around its memory to render different objects.
I also understand that if I need to render objects with different vertex attributes, then a new VAO is necessary in this case.
If that "it depends" really is quite variable, what's best for a beginner with OpenGL, assuming that better approaches can be learnt later with better understanding?

• 13
• 12
• 10
• 12
• 22