Jump to content

Help tracking down GPU memory leak


Recommended Posts

Hi all,

I'm having trouble tracking down a GPU memory leak. I'm using chrome's process explorer to see how much memory my game/tab is taking up. Every time a user starts a new level, it adds about 40MB of GPU memory. Here's what we're doing every level load:

  • stage.destroy({ children: true, texture: false, baseTexture: false }) // not destroying all textures as we want to reuse them next run
  • pixiRenderer.destroy(true)

I don't know of any obvious places we'd be leaking textures or anything else.

1) Is there a centralized place we could look for resources that are growing? (lists in TextureSystem, etc..?)

2) Is there any webgl commands I should look out for that pixi is calling that I could track somehow, to see what is growing the GPU memory?

I'd like it if I could find out what is allocating GPU memory but don't know where to start.



Link to comment
Share on other sites

Right now I'm just using a single 1x1 rendertexture to preload some textures/shaders. This is destroyed immediately after use.

I've looked into this further and we're leaking regular js mem quite a bit. We've got pixi renderers staying in memory because of this. Is it possible that this could cause GPU leaks? Either way I'm going to clean up these leaks (hopefully!) and see where we're at then.

Thanks Ivan.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Create New...