Stop/Test lingering objects

[Halsafar]

Alright, I am trying to capture all the basic ways to exit a program and to deal with the unloading of all the important objects like Dx interfaces for example.

Is there a way to test if I missed any? Like get size at beginning and end or something.

Now, what if the game stalls, exception handle, a user terminates it with ctrl+alt+del...some sort of error which cause's instant termination...

Is there a way to deal with that? Like to make sure things unload, it is my idea that if some sort of unexpected termination occurs then memory leaks would follow.

[CornedBee]

There is always a way to kill your app that can't be caught. The simplest is to call TerminateProcess. It's zaps your app immediately. You don't get a single instruction for cleanup. You can't even block it.

Similarly, the abort() CRT function kills your process without giving anyone a chance to clean up.
exit() only calls the functions registered with atexit().

However, these are unusual circumstances. In a C++ program, calling exit() somewhere high up in the stack is usually a bad idea. To deal with everything else (exceptions and friends), use RAII: everything that needs to be cleaned up ought to be wrapped at least in a simple holder object that frees it on destruction.

[Halsafar]

That said, s`all a good idea.
I suppose kind of useless for most apps.

So no way to double-check I am hitting an unload everytime on a plain regular exit from WinMain?

[CornedBee]

What?