Hi,
While testing our game we noticed that one player seems to get crashes very often. After checking the acklog.txt, it seems that there's always a "nexus overflow" towards the end of the file.

Now, the manual says that a nexus overflow can theoretically not crash the program, but aparrently directX can crash.
So I checked the Task Manager and noticed that the Amount of Memory used by the Program slowly increases over time.

How do I find these leaks? Is there an easy way or do I have to go through every str_create, pan_create ... (my program's rather long) and check?
And is this the reason my Program crashes?
Edit: and if so, why does it crash on a PC that has about the same amount of memory that I have?

Edit: One more thing... max_nexus is around 40960, while nexus is around 158646, so, around 4 times as much...

Does no one answering mean I have to go through every pan_create, str_create etc. manually? there's no way to make acknex output more info before the crash or something?
Darn. This will take me quite some time.

Memory is usually allocated in the stack f.i. when u define local variables the memory is freed after the function is terminated.
But if you allocate memory urself (with new, malloc or any create command) its stored in the heap - and you have to free it urself(with delete resp- engine objects with ptr_remove). Otherwise you get memory leaks.

I think that he knew that already

@Germanunkol: There are a few memory tracker, like Valgrind or Instruments. The down side: Non of these works on Windows. The first one is for UNIX and the the second one is for Mac OS. Another great thing would be D-Trace, but this needs kernel support (you could file an enhancement request at microsoft :P).

However, all the tools track only real leaks, but you still have A7/A8 as wrapper which releases everything allocated via xxx_create and sys_malloc at the end (at least it should).

But what you can do is the following: Create a macro with the name ent_create which takes all too parameters. This than calls a function that logs the creation (name of the file, action etc. so you can track the Entity created. Or! Say that you want the __FILE__ and __LINE__ macros. Than you can track the file and line that creates something.)
After you created the log entry, you can pass everything to the real xxx_create function. If you are done with testing, just remove the macros and everything is fine again

Edit: Of course you should also overwrite the xxx_remove functions to track which objects stay alive even if they aren't used anymore.