Sign in to follow this  
Tordin

DX11 [DX11] Memory leeks that i cant get ridoff

Recommended Posts

Hello!

I noticed that i got memory leaks from the dx debug device.
i have been on this for ever trying to solve it but how hard i try i still get the same ones...

Example :

D3D11: WARNING: Live Device: Name="unnamed", Addr=0x00286EE8, ExtRef=1 [ STATE_CREATION WARNING #2097297: LIVE_DEVICE ]
D3D11: WARNING: Live Texture2D: Name="unnamed", Addr=0x00288E4C, ExtRef=0, IntRef=0 [ STATE_CREATION WARNING #2097235: LIVE_TEXTURE2D ]
D3D11: WARNING: Live Query: Name="unnamed", Addr=0x002889EC, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097280: LIVE_QUERY ]
D3D11: WARNING: Live Sampler: Name="unnamed", Addr=0x002887B4, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097268: LIVE_SAMPLER ]
D3D11: WARNING: Live RasterizerState: Name="unnamed", Addr=0x0028858C, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097277: LIVE_RASTERIZERSTATE ]
D3D11: WARNING: Live DepthStencilState: Name="unnamed", Addr=0x00288404, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097274: LIVE_DEPTHSTENCILSTATE ]
D3D11: WARNING: Live BlendState: Name="unnamed", Addr=0x0028CDA4, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097271: LIVE_BLENDSTATE ]
D3D11: WARNING: Live Context: Name="unnamed", Addr=0x0228006C, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097226: LIVE_CONTEXT ]
D3D11: WARNING: Live Device Child Summary: Device Addr=0x00286EE8

When i google the warnings i only get post about ppl who havent released it right, but i are more than sure that i have!

Any clues Internet?

Share this post


Link to post
Share on other sites
[quote name='Tordin' timestamp='1312591384' post='4845293']
Hello!

I noticed that i got memory leaks from the dx debug device.
i have been on this for ever trying to solve it but how hard i try i still get the same ones...

Example :

D3D11: WARNING: Live Device: Name="unnamed", Addr=0x00286EE8, ExtRef=1 [ STATE_CREATION WARNING #2097297: LIVE_DEVICE ]
D3D11: WARNING: Live Texture2D: Name="unnamed", Addr=0x00288E4C, ExtRef=0, IntRef=0 [ STATE_CREATION WARNING #2097235: LIVE_TEXTURE2D ]
D3D11: WARNING: Live Query: Name="unnamed", Addr=0x002889EC, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097280: LIVE_QUERY ]
D3D11: WARNING: Live Sampler: Name="unnamed", Addr=0x002887B4, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097268: LIVE_SAMPLER ]
D3D11: WARNING: Live RasterizerState: Name="unnamed", Addr=0x0028858C, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097277: LIVE_RASTERIZERSTATE ]
D3D11: WARNING: Live DepthStencilState: Name="unnamed", Addr=0x00288404, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097274: LIVE_DEPTHSTENCILSTATE ]
D3D11: WARNING: Live BlendState: Name="unnamed", Addr=0x0028CDA4, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097271: LIVE_BLENDSTATE ]
D3D11: WARNING: Live Context: Name="unnamed", Addr=0x0228006C, ExtRef=0, IntRef=1 [ STATE_CREATION WARNING #2097226: LIVE_CONTEXT ]
D3D11: WARNING: Live Device Child Summary: Device Addr=0x00286EE8

When i google the warnings i only get post about ppl who havent released it right, but i are more than sure that i have!

Any clues Internet?
[/quote]

Trust me, you haven't. I'm currently working on a planet renderer and everytime I get memory leaks, I find that I, indeed had some obscure situation where they weren't released. Try slowly commenting out code sections until you get a clean exit.

Share this post


Link to post
Share on other sites
The list shows that you have an outstanding device reference. What happens if you do a double release on your device before exiting the program? You can also check the status of the objects with PIX to see if there is something that you hadn't considered before...

Share this post


Link to post
Share on other sites
Try setting debug names for all the Direct3D objects you create - that includes device, textures, buffers, states, etc... Then this debug display will include name of object that is alive (instead of name="unamed"). For textures, for example, use name of file you load. For buffers use name of mesh/model you are storing there, and so on.

Do it like this: http://msdn.microsoft.com/en-us/library/ff476881.aspx

Then you will exactly which objects are alive.

Share this post


Link to post
Share on other sites
[quote name='Jason Z' timestamp='1312614076' post='4845347']
The list shows that you have an outstanding device reference. What happens if you do a double release on your device before exiting the program? You can also check the status of the objects with PIX to see if there is something that you hadn't considered before...
[/quote]


Nice, that got rid of everything for me!

How come i have to do it twice?


Share this post


Link to post
Share on other sites
Are you calling on some object like buffer, or shader GetDevice method? GetDevice method increments reference count by one, so you should also add Release call after you process device returned by GetDevice method.

Share this post


Link to post
Share on other sites
As MartinsM says everytime you use GetDevice or GetBuffer it actually increments a reference counter.

This means if you don't release after you've done these functions it'll warn that some objects and anything linked to it are still active.

Calling release at these points decreases the ref counter and the object is still alive.

For example

[code]ID3D11Texture2D* pBackBuffer = nullptr;
if(FAILED(swapChain_->GetBuffer( 0, __uuidof( ID3D11Texture2D ), ( void** )&pBackBuffer ))) //increments ref counter
{
MessageBox( NULL, "Failed to get the back buffer.", "Error", MB_OK );
return false;
}

if(FAILED(device_->CreateRenderTargetView( pBackBuffer, NULL, renderTarget)))
{
MessageBox( NULL, "Failed to create a render target from the back buffer.", "Error creating render target", MB_OK );
return false;
}
pBackBuffer->Release(); // called release to decrease ref counter
[/code]

Aside from this its mostly a case of looking for sampler/blender/rasterizer states that haven't been released.

Share this post


Link to post
Share on other sites
And if you are not comfortable with calling manually Release, then simply use CComPtr (from atlbase.h) everywhere instead of raw ID3D11xyz pointers:
[code]{
CComPtr<ID3D11Texture2D> pBackBuffer;
if(FAILED(swapChain_->GetBuffer( 0, __uuidof( ID3D11Texture2D ), ( void** )&pBackBuffer ))) //increments ref counter
{
MessageBox( NULL, "Failed to get the back buffer.", "Error", MB_OK );
return false;
}

if(FAILED(device_->CreateRenderTargetView( pBackBuffer, NULL, renderTarget)))
{
MessageBox( NULL, "Failed to create a render target from the back buffer.", "Error creating render target", MB_OK );
return false;
}
} // no need to call pBackBuffer->Release(), it will be called automatically[/code]

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  

  • Partner Spotlight

  • Forum Statistics

    • Total Topics
      627662
    • Total Posts
      2978506
  • Similar Content

    • By evelyn4you
      hi,
      i have read very much about the binding of a constantbuffer to a shader but something is still unclear to me.
      e.g. when performing :   vertexshader.setConstantbuffer ( buffer,  slot )
       is the buffer bound
      a.  to the VertexShaderStage
      or
      b. to the VertexShader that is currently set as the active VertexShader
      Is it possible to bind a constantBuffer to a VertexShader e.g. VS_A and keep this binding even after the active VertexShader has changed ?
      I mean i want to bind constantbuffer_A  to VS_A, an Constantbuffer_B to VS_B  and  only use updateSubresource without using setConstantBuffer command every time.

      Look at this example:
      SetVertexShader ( VS_A )
      updateSubresource(buffer_A)
      vertexshader.setConstantbuffer ( buffer_A,  slot_A )
      perform drawcall       ( buffer_A is used )

      SetVertexShader ( VS_B )
      updateSubresource(buffer_B)
      vertexshader.setConstantbuffer ( buffer_B,  slot_A )
      perform drawcall   ( buffer_B is used )
      SetVertexShader ( VS_A )
      perform drawcall   (now which buffer is used ??? )
       
      I ask this question because i have made a custom render engine an want to optimize to
      the minimum  updateSubresource, and setConstantbuffer  calls
       
       
       
       
       
    • By noodleBowl
      I got a quick question about buffers when it comes to DirectX 11. If I bind a buffer using a command like:
      IASetVertexBuffers IASetIndexBuffer VSSetConstantBuffers PSSetConstantBuffers  and then later on I update that bound buffer's data using commands like Map/Unmap or any of the other update commands.
      Do I need to rebind the buffer again in order for my update to take effect? If I dont rebind is that really bad as in I get a performance hit? My thought process behind this is that if the buffer is already bound why do I need to rebind it? I'm using that same buffer it is just different data
       
    • By Rockmover
      I am really stuck with something that should be very simple in DirectX 11. 
      1. I can draw lines using a PC (position, colored) vertices and a simple shader just fine.
      2. I can draw 3D triangles using PCN (position, colored, normal) vertices just fine (even transparency and SpecularBlinnPhong shaders).
       
      However, if I'm using my 3D shader, and I want to draw my PC lines in the same scene how can I do that?
       
      If I change my lines to PCN and pass them to the 3D shader with my triangles, then the lighting screws them all up.  I only want the lighting for the 3D triangles, but no SpecularBlinnPhong/Lighting for the lines (just PC). 
      I am sure this is because if I change the lines to PNC there is not really a correct "normal" for the lines.  
      I assume I somehow need to draw the 3D triangles using one shader, and then "switch" to another shader and draw the lines?  But I have no clue how to use two different shaders in the same scene.  And then are the lines just drawn on top of the triangles, or vice versa (maybe draw order dependent)?  
      I must be missing something really basic, so if anyone can just point me in the right direction (or link to an example showing the implementation of multiple shaders) that would be REALLY appreciated.
       
      I'm also more than happy to post my simple test code if that helps as well!
       
      THANKS SO MUCH IN ADVANCE!!!
    • By Reitano
      Hi,
      I am writing a linear allocator of per-frame constants using the DirectX 11.1 API. My plan is to replace the traditional constant allocation strategy, where most of the work is done by the driver behind my back, with a manual one inspired by the DirectX 12 and Vulkan APIs.
      In brief, the allocator maintains a list of 64K pages, each page owns a constant buffer managed as a ring buffer. Each page has a history of the N previous frames. At the beginning of a new frame, the allocator retires the frames that have been processed by the GPU and frees up the corresponding space in each page. I use DirectX 11 queries for detecting when a frame is complete and the ID3D11DeviceContext1::VS/PSSetConstantBuffers1 methods for binding constant buffers with an offset.
      The new allocator appears to be working but I am not 100% confident it is actually correct. In particular:
      1) it relies on queries which I am not too familiar with. Are they 100% reliable ?
      2) it maps/unmaps the constant buffer of each page at the beginning of a new frame and then writes the mapped memory as the frame is built. In pseudo code:
      BeginFrame:
          page.data = device.Map(page.buffer)
          device.Unmap(page.buffer)
      RenderFrame
          Alloc(size, initData)
              ...
              memcpy(page.data + page.start, initData, size)
          Alloc(size, initData)
              ...
              memcpy(page.data + page.start, initData, size)
      (Note: calling Unmap at the end of a frame prevents binding the mapped constant buffers and triggers an error in the debug layer)
      Is this valid ? 
      3) I don't fully understand how many frames I should keep in the history. My intuition says it should be equal to the maximum latency reported by IDXGIDevice1::GetMaximumFrameLatency, which is 3 on my machine. But, this value works fine in an unit test while on a more complex demo I need to manually set it to 5, otherwise the allocator starts overwriting previous frames that have not completed yet. Shouldn't the swap chain Present method block the CPU in this case ?
      4) Should I expect this approach to be more efficient than the one managed by the driver ? I don't have meaningful profile data yet.
      Is anybody familiar with the approach described above and can answer my questions and discuss the pros and cons of this technique based on his experience ? 
      For reference, I've uploaded the (WIP) allocator code at https://paste.ofcode.org/Bq98ujP6zaAuKyjv4X7HSv.  Feel free to adapt it in your engine and please let me know if you spot any mistakes
      Thanks
      Stefano Lanza
       
    • By Matt Barr
      Hey all. I've been working with compute shaders lately, and was hoping to build out some libraries to reuse code. As a prerequisite for my current project, I needed to sort a big array of data in my compute shader, so I was going to implement quicksort as a library function. My implementation was going to use an inout array to apply the changes to the referenced array.

      I spent half the day yesterday debugging in visual studio before I realized that the solution, while it worked INSIDE the function, reverted to the original state after returning from the function.

      My hack fix was just to inline the code, but this is not a great solution for the future.  Any ideas? I've considered just returning an array of ints that represents the sorted indices.
  • Popular Now