• Advertisement
Sign in to follow this  

OpenGL Ensuring proper cleanup of GPU memory in OpenGL

Recommended Posts

I am wondering what are some good  strategies to make sure I am definitely cleaning up all my GPU allocated memory when I exit a level. I plan to allocate/de-allocate on a per-level basis. I am using the OpenGL 4.x C++ API. 

My thought was maybe:

1.  measure GPU memory,
2. instantiate a level, then delete it
3. measure GPU memory again and verify that its the same amount.

I am not sure if functions exist to even accurately measure GPU memory used by a process.. I see there are some functions that I could use on my NVidia card, such as the one mentioned here: http://www.geeks3d.com/20100531/programming-tips-how-to-know-the-graphics-memory-size-and-usage-in-opengl/ 
but I think that only operates at the Kilobyte level...

Alternatively, I believe all the GPU memory allocated for my level will be local to my GL Context. So maybe I could delete and re-create the context, but I'd have to do this through SDL and wonder if this would be practical, or good practice to do between levels.

Suggestions and advice are appreciated!

 

Share this post


Link to post
Share on other sites
Advertisement

It looks like, in theory, I could use:

    SDL_GL_DeleteContext(mainGLContext);
    mainGLContext = SDL_GL_CreateContext(mainWindow);

Between levels... not sure how common this approach would be...

Share this post


Link to post
Share on other sites
Assuming that your code is correct and doesn't leak, this will have no benefit and only make your loading screens take longer.

I wrap up every GL function that allocates memory and convert them into my own handles. I can then place these handles into an internal list to keep track of active allocations. Whenever I call a GL function that deletes memory I assert that a matching handle is present in my list and then remove it.

Share this post


Link to post
Share on other sites

Keep a list of all GL objects allocated for you level, during your level transitions delete all objects from that list - simple as.

How to verify that it actually has been deleted?  You can't and you probably shouldn't worry about it.

A GL implementation may have it's own memory management strategies, and deleting a GL object (via a glDelete* call) is only guaranteed to make the object name available for immediate re-use.

If you want absolute control over memory then use Vulkan.  Otherwise this is something that nobody worries about in GL.

Share this post


Link to post
Share on other sites

It looks like, in theory, I could use:

    SDL_GL_DeleteContext(mainGLContext);
    mainGLContext = SDL_GL_CreateContext(mainWindow);

Between levels... not sure how common this approach would be...

No! ... just ... no ...

Share this post


Link to post
Share on other sites

It looks like, in theory, I could use:

SDL_GL_DeleteContext(mainGLContext);    mainGLContext = SDL_GL_CreateContext(mainWindow);
Between levels... not sure how common this approach would be...
Destroying and recreating the context is as much of a heavyweight operation as can be, only topped by rebooting the computer. I wouldn't advise doing that.

Keeping track of what objects exist is no magic (in fact, in a correct program it's pretty much a prerequisite that you know, not just about GL objects), so deleting what you no longer need shouldn't really be magic either. There is no verifying that your stuff has been deleted, and no reason why you should need that.
GL does an awful lot of management (and abstraction) for you, and while that's sometimes annoying when you want the bleeding edge, the good thing is that it frees you from worrying about such nitpicks. It also means for example that in the worst case you can just call exit(0) when your game exits. While morally wrong, this will work just fine with OpenGL, the driver will clean up behind you. Try doing that with Vulkan, good luck (on my machine, you do this a couple of times, then the display driver crashes).

So... deleting an object doesn't guarantee that the memory is freed, that's right. Just forget about it. It's somebody else's problem to make it work!

measure GPU memory

OpenGL deliberately doesn't let you do that (though some IHVs have extensions for that). You shouldn't know, nor want to know, how much GPU memory is free. Again, that's both a blessing and a curse, it depends on the situation. Measuring twice and making sure the amount of free memory is the same won't work anyway. That's almost guaranteed to fail.

Share this post


Link to post
Share on other sites
On the original question, I think that if you capture a frame in Renderdoc with the "ref all initials" option ticked (or something like that), then it will let you view a full list of textures/buffers.
You could capture a frame before loading a level and after quitting that level, and then manually verify these lists are the same in both captures.

Share this post


Link to post
Share on other sites

Thank you all for your input!

On the original question, I think that if you capture a frame in Renderdoc with the "ref all initials" option ticked (or something like that), then it will let you view a full list of textures/buffers.
You could capture a frame before loading a level and after quitting that level, and then manually verify these lists are the same in both captures.

 

Yes! Ideas like this are what I'm looking for. On my engine, I have been lazy about memory management on both GPU and CPU (hence a similar post on the general programming forum for C++ cleanup) and I'm paying the price for it now. Trying to make sure I have all my cleanup in place, and looking for a way to check that I have been thorough.. 

Share this post


Link to post
Share on other sites

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

Sign in

Already have an account? Sign in here.

Sign In Now

Sign in to follow this  

  • Advertisement
  • Advertisement
  • Popular Tags

  • Advertisement
  • Popular Now

  • Similar Content

    • By LifeArtist
      Good Evening,
      I want to make a 2D game which involves displaying some debug information. Especially for collision, enemy sights and so on ...
      First of I was thinking about all those shapes which I need will need for debugging purposes: circles, rectangles, lines, polygons.
      I am really stucked right now because of the fundamental question:
      Where do I store my vertices positions for each line (object)? Currently I am not using a model matrix because I am using orthographic projection and set the final position within the VBO. That means that if I add a new line I would have to expand the "points" array and re-upload (recall glBufferData) it every time. The other method would be to use a model matrix and a fixed vbo for a line but it would be also messy to exactly create a line from (0,0) to (100,20) calculating the rotation and scale to make it fit.
      If I proceed with option 1 "updating the array each frame" I was thinking of having 4 draw calls every frame for the lines vao, polygons vao and so on. 
      In addition to that I am planning to use some sort of ECS based architecture. So the other question would be:
      Should I treat those debug objects as entities/components?
      For me it would make sense to treat them as entities but that's creates a new issue with the previous array approach because it would have for example a transform and render component. A special render component for debug objects (no texture etc) ... For me the transform component is also just a matrix but how would I then define a line?
      Treating them as components would'nt be a good idea in my eyes because then I would always need an entity. Well entity is just an id !? So maybe its a component?
      Regards,
      LifeArtist
    • By QQemka
      Hello. I am coding a small thingy in my spare time. All i want to achieve is to load a heightmap (as the lowest possible walking terrain), some static meshes (elements of the environment) and a dynamic character (meaning i can move, collide with heightmap/static meshes and hold a varying item in a hand ). Got a bunch of questions, or rather problems i can't find solution to myself. Nearly all are deal with graphics/gpu, not the coding part. My c++ is on high enough level.
      Let's go:
      Heightmap - i obviously want it to be textured, size is hardcoded to 256x256 squares. I can't have one huge texture stretched over entire terrain cause every pixel would be enormous. Thats why i decided to use 2 specified textures. First will be a tileset consisting of 16 square tiles (u v range from 0 to 0.25 for first tile and so on) and second a 256x256 buffer with 0-15 value representing index of the tile from tileset for every heigtmap square. Problem is, how do i blend the edges nicely and make some computationally cheap changes so its not obvious there are only 16 tiles? Is it possible to generate such terrain with some existing program?
      Collisions - i want to use bounding sphere and aabb. But should i store them for a model or entity instance? Meaning i have 20 same trees spawned using the same tree model, but every entity got its own transformation (position, scale etc). Storing collision component per instance grats faster access + is precalculated and transformed (takes additional memory, but who cares?), so i stick with this, right? What should i do if object is dynamically rotated? The aabb is no longer aligned and calculating per vertex min/max everytime object rotates/scales is pretty expensive, right?
      Drawing aabb - problem similar to above (storing aabb data per instance or model). This time in my opinion per model is enough since every instance also does not have own vertex buffer but uses the shared one (so 20 trees share reference to one tree model). So rendering aabb is about taking the model's aabb, transforming with instance matrix and voila. What about aabb vertex buffer (this is more of a cosmetic question, just curious, bumped onto it in time of writing this). Is it better to make it as 8 points and index buffer (12 lines), or only 2 vertices with min/max x/y/z and having the shaders dynamically generate 6 other vertices and draw the box? Or maybe there should be just ONE 1x1x1 cube box template moved/scaled per entity?
      What if one model got a diffuse texture and a normal map, and other has only diffuse? Should i pass some bool flag to shader with that info, or just assume that my game supports only diffuse maps without fancy stuff?
      There were several more but i forgot/solved them at time of writing
      Thanks in advance
    • By RenanRR
      Hi All,
      I'm reading the tutorials from learnOpengl site (nice site) and I'm having a question on the camera (https://learnopengl.com/Getting-started/Camera).
      I always saw the camera being manipulated with the lookat, but in tutorial I saw the camera being changed through the MVP arrays, which do not seem to be camera, but rather the scene that changes:
      Vertex Shader:
      #version 330 core layout (location = 0) in vec3 aPos; layout (location = 1) in vec2 aTexCoord; out vec2 TexCoord; uniform mat4 model; uniform mat4 view; uniform mat4 projection; void main() { gl_Position = projection * view * model * vec4(aPos, 1.0f); TexCoord = vec2(aTexCoord.x, aTexCoord.y); } then, the matrix manipulated:
      ..... glm::mat4 projection = glm::perspective(glm::radians(fov), (float)SCR_WIDTH / (float)SCR_HEIGHT, 0.1f, 100.0f); ourShader.setMat4("projection", projection); .... glm::mat4 view = glm::lookAt(cameraPos, cameraPos + cameraFront, cameraUp); ourShader.setMat4("view", view); .... model = glm::rotate(model, glm::radians(angle), glm::vec3(1.0f, 0.3f, 0.5f)); ourShader.setMat4("model", model);  
      So, some doubts:
      - Why use it like that?
      - Is it okay to manipulate the camera that way?
      -in this way, are not the vertex's positions that changes instead of the camera?
      - I need to pass MVP to all shaders of object in my scenes ?
       
      What it seems, is that the camera stands still and the scenery that changes...
      it's right?
       
       
      Thank you
       
    • By dpadam450
      Sampling a floating point texture where the alpha channel holds 4-bytes of packed data into the float. I don't know how to cast the raw memory to treat it as an integer so I can perform bit-shifting operations.

      int rgbValue = int(textureSample.w);//4 bytes of data packed as color
      // algorithm might not be correct and endianness might need switching.
      vec3 extractedData = vec3(  rgbValue & 0xFF000000,  (rgbValue << 8) & 0xFF000000, (rgbValue << 16) & 0xFF000000);
      extractedData /= 255.0f;
    • By Devashish Khandelwal
      While writing a simple renderer using OpenGL, I faced an issue with the glGetUniformLocation function. For some reason, the location is coming to be -1.
      Anyone has any idea .. what should I do?
  • Advertisement