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

Memory leaks are always contained inside processes, aren't they?

9 posts in this topic

I acknowledge the fact that memory leaks are bad, regardless of if you're doing it on purpose or not.

 

I do notice there's a behavior in memory leaks, such that if a program were to create memory leaks, Windows 7's Task Manager will always show the program's name and process in the list even if the program had already been closed. Same applies to MSBuild for Visual Studios, if the affected program left behind tons of unresolved commands, we kill the process in Task Manager.

 

My guess is that memory leaks are always contained and recollected back into the resource pool when the affected process has been killed by Task Manager. And that there is no way to create a memory leak that is persistent and permanently damaging to the RAM in the computer... am I right in this?

struct Object
{
	int hello;
	bool world;
};

void purposefullyCreateMemoryLeak(){
	Object** ptr = new Object*[200];
	for (int i = 0; i < 200; i++){
		ptr[i] = new Object;
		ptr[i]->hello = 20 - i;
		ptr[i]->world = false;
	}
	//Gracefully return and leave behind memory leak.
	return;
}

They say that hackers can create physical damage to hardware components just by software alone. If they are able to create memory leaks and not make it so that it's impossible to be isolated within a process that had quit, it will be a tough day for a researcher.

0

Share this post


Link to post
Share on other sites

The definition of a memory leak is more than just memory being used and not freeing when it should, it has to do with not having direct access as a developer to that area of memory, ie: a loss of control.

 

Sometimes when you close a program, depending on how that programs closing event was programmed, it will handle memory clean up in some manual way, perhaps there is finalizing/handshaking mechanics that are going on it the background, or its possible that the OS is doing some magic to try and release the memory.

Edited by d4n1
0

Share this post


Link to post
Share on other sites

Most memory leaks are contained within the running process, but some are not, especially, GDI leaks. If you run out of handles, well, you're os might start to act/look strangely.

Neither of them are damaging to memory, but with the second case you will have to reboot your computer.

 

I would be very surprise if hackers could actually manage to break things in a computer nowaday. Maybe through some overclocking hack?(i doubt it)

What 'people say' and what is real is often quite different. Since i can't say for 100% sure that this can't happen, i'll let others step in, but it's doubtfull at best.

 

I remember of one virus, CIH, that could do damage to computers, through changing some bios settings, but it was a long time ago.

1

Share this post


Link to post
Share on other sites
While you mentioned 'processes' several times, your code showed a function, not a process.

So just to be clear, memory leaks do persist after the function ends.
void purposefullyCreateMemoryLeak()
{
	Object *ptr = new Object;
	return;
}

void funcB()
{
    purposefullyCreateMemoryLeak();
    
    //Memory is still leaked!
    return;
}

void funcA()
{
    funcB();
    
    //Memory is still leaked!
    return;
}

int main()
{
    funcA();
    
    //Memory is still leaked!    

    //Sometime after main() exits (and after the function(s) that originally called main() exits),
    //then the memory will most likely be cleaned up by the operating system.
    return 0;
}
It's considered good practice to clean up after yourself, when programming - though if your code is trying to shut down because something went wrong (i.e. the program is crashing in a controlled manner), leaked resources aren't the end of the world.
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