• Announcements

    • khawk

      Download the Game Design and Indie Game Marketing Freebook   07/19/17

      GameDev.net and CRC Press have teamed up to bring a free ebook of content curated from top titles published by CRC Press. The freebook, Practices of Game Design & Indie Game Marketing, includes chapters from The Art of Game Design: A Book of Lenses, A Practical Guide to Indie Game Marketing, and An Architectural Approach to Level Design. The GameDev.net FreeBook is relevant to game designers, developers, and those interested in learning more about the challenges in game development. We know game development can be a tough discipline and business, so we picked several chapters from CRC Press titles that we thought would be of interest to you, the GameDev.net audience, in your journey to design, develop, and market your next game. The free ebook is available through CRC Press by clicking here. The Curated Books The Art of Game Design: A Book of Lenses, Second Edition, by Jesse Schell Presents 100+ sets of questions, or different lenses, for viewing a game’s design, encompassing diverse fields such as psychology, architecture, music, film, software engineering, theme park design, mathematics, anthropology, and more. Written by one of the world's top game designers, this book describes the deepest and most fundamental principles of game design, demonstrating how tactics used in board, card, and athletic games also work in video games. It provides practical instruction on creating world-class games that will be played again and again. View it here. A Practical Guide to Indie Game Marketing, by Joel Dreskin Marketing is an essential but too frequently overlooked or minimized component of the release plan for indie games. A Practical Guide to Indie Game Marketing provides you with the tools needed to build visibility and sell your indie games. With special focus on those developers with small budgets and limited staff and resources, this book is packed with tangible recommendations and techniques that you can put to use immediately. As a seasoned professional of the indie game arena, author Joel Dreskin gives you insight into practical, real-world experiences of marketing numerous successful games and also provides stories of the failures. View it here. An Architectural Approach to Level Design This is one of the first books to integrate architectural and spatial design theory with the field of level design. The book presents architectural techniques and theories for level designers to use in their own work. It connects architecture and level design in different ways that address the practical elements of how designers construct space and the experiential elements of how and why humans interact with this space. Throughout the text, readers learn skills for spatial layout, evoking emotion through gamespaces, and creating better levels through architectural theory. View it here. Learn more and download the ebook by clicking here. Did you know? GameDev.net and CRC Press also recently teamed up to bring GDNet+ Members up to a 20% discount on all CRC Press books. Learn more about this and other benefits here.
Sign in to follow this  
Followers 0
ericrrichards22

Disposing of Textures with DebugNames

3 posts in this topic

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?

0

Share this post


Link to post
Share on other sites
Hmmm, one could either consider this a bug in the implementation or a wrong usage of the Resource property. Usually a D3D11 API GetWhatEver functions increases the reference counter (see remarks of ID3D11View::GetResource). This happens when reading the C# property. I don't see a Release/Dispose counterpart here, so you need to do one yourself. Should work fine when doing that immediately after setting the debug name.

Alternatives:
- Use textures explicitly and don't directly create SRVs.
- Use the debug name on the SRV, not the texture
1

Share this post


Link to post
Share on other sites

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.

Edited by Bacterius
1

Share this post


Link to post
Share on other sites

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.

0

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  
Followers 0