When creating ShaderResourceViews in my engine, I've started assigning them DebugName properties to assist in debugging, using the VS 2013 graphics debugger. I've noticed that since I've started doing this, the underlying Texture objects aren't getting disposed of correctly, and SlimDX complains of memory leaks when the program closes. The code to create a ShaderResourceView looks like this:

CubeMapSRV = ShaderResourceView.FromFile(device, filename);
CubeMapSRV.Resource.DebugName = "sky cubemap";

The code to dispose of the ShaderResourceView looks like this:

if (CubeMapSRV != null){
    CubeMapSRV.Dispose();
    CubeMapSRV = null;
}

The object creation stack trace printed by SlimDX is indicating that it is the CubeMapSRV.Resource.DebugName assignment that is leaking; specifically, the underlying Texture object. Is assigning the DebugName creating a reference to the Texture somewhere that is hidden from me?

I ran into the same problem a few days ago. As unbird mentions you must dispose of any device resource you acquire a reference to by calling Get* functions. One thing to remember is that Dispose() does not destroy the resource, it simply decreases the reference count and invalidates said reference, the resource itself is only destroyed when it hits zero. So in theory this should work:

using (Resource resource = CubeMapSRV.Resource)
{
    resource.DebugName = "sky cubemap";
}

In practice, I prefer to avoid messing around with reference counters and instead created a helper class which stores a resource and provides non-reference-counted access to SRV's, RTV's, UAV's, ... By the way, this problem also applies to ImmediateContext and a bunch of other stuff, and you don't need to set variables to null after disposing them. I think the underlying issue is that the C# memory management model does not quite map to how DirectX works, so you need to be a bit more careful with what you do to avoid making incorrect assumptions.

Thanks for the explanations. I've ended up going with assigning the DebugName inside a using, as Bacterius suggested. Disposing of the SRV's Resource property also works, but I found it a little more cumbersome.

you don't need to set variables to null after disposing them

Mainly, I am doing this in order to make sure I'm not accessing anything after it's been disposed; the bulk of my SlimDX ComObjects are bound up in my game objects, so for all intents and purposes, when I Dispose of a game object, I want it to return the game object to a completely uninitialized state.