• 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
najmuddin

Dynamic memory and forced process closing

5 posts in this topic

Greetings!

I would like to ask you what does happen whith the variables on the dynamic memory (created with [b]new[/b]) if you force the closing of the process, before the call of the [b]delete[/b] instruction?... Are destroyers called anyway?... What are the consequences of that?

Thank you... (And sorry, I'm bad speaking english)
0

Share this post


Link to post
Share on other sites
Destructors are not called, no, but since dynamic memory is managed by the OS, when your process dies, the operating system cleans everything up for you anyway (and same for most resources like file descriptors, sockets, etc..). That doesn't mean you should not care to free your memory before ending your program, you should always do it, because if you need to save your program's state to disk somehow, you'll have to make sure it's done because the operating system won't do that for you, but it does mean you need not worry about memory getting lost when your process is killed.

Actually, it depends what you mean by "forcing" the process to close. There's a big difference between an API like TerminateProcess() and ExitProcess() under Windows, for instance.
1

Share this post


Link to post
Share on other sites
[quote name='Khatharr' timestamp='1354674938' post='5007282']
Does TerminateProcess() not release the pages of the target process?
[/quote]
No, all virtual memory is released when the process is terminated (though the process may take a while to terminate as I/O is difficult to interrupt, at least under Windows). However the program (or attached libraries) may need to do special cleanup work which TerminateProcess() won't let them do, unlike ExitProcess().
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