Page 1 of 1
[fixed for V0.36] Memory errors on exit.
Posted: Thu Mar 09, 2006 2:59 am
by Gambit37
I'm regularly getting errors on exiting the editor:
RTC Editor (V0.35) Diagnostic file - Thu Mar 09 01:56:52 2006
Error:
an access violation exception.
Stack Dump:
utilMemory.utilVerifyMemory();
RTCEditApp.ExitInstance();
Posted: Thu Mar 09, 2006 7:04 am
by Sophia
I got this error many times during beta testing, too... but I could never pin down just what was causing it. The closest I ever got was "adding and deleting lots of stuff makes it happen more often."
Real helpful, I know.

Posted: Thu Mar 09, 2006 1:17 pm
by George Gilbert
As Sophia said, this has been seen before, but without a reproducible scenario it's going to be impossible to track down.
If it helps, the function thats crashing is checking that all the memory that was malloc-ed has also been freed (i.e. it's checking for memory leaks) and it's (intentionally) crashing because it's found a mismatch.
Therefore, the source of the problem is probably the creation of a new object or other resource possibly followed by a delete of it.
If you can narrow it down any further it would be very helpful!
Posted: Fri Mar 10, 2006 2:14 pm
by George Gilbert
Fixed all of this for V0.36 (or at least, I've fixed *a* memory leak - whether it's *the* memory leak you were seeing, is another matter altogether!).
Posted: Sun Mar 12, 2006 11:55 am
by Gambit37
Just got a memory error in RTC Editor: Loaded my custom dungeon with the new wallset (just remembered there are acouple of replacement sounds in it too). Added an alpha PNG to replace the monster death cloud. Saved and exited, and got the error after that. Standard message:
RTC Editor (V0.35) Diagnostic file - Sun Mar 12 10:52:51 2006
Error:
an access violation exception.
Stack Dump:
utilMemory.utilVerifyMemory();
RTCEditApp.ExitInstance();
Programs running: Firefox, Windows Explorer, Photoshop plus usual standard stuff: firewall, anti virus, etc...
Posted: Sun Mar 12, 2006 1:10 pm
by George Gilbert
Gambit37 wrote:Added an alpha PNG to replace the monster death cloud.
That's the memory leak I fixed (replacing resources leaks memory)...
Clearly, the key question is - is there another one?