24 Jun
2005
24 Jun
'05
6:32 p.m.
Incidentally, while it's good to solve memory leaks, the problem I've been trying to diagnose is the one in this bug:
http://sourceforge.net/tracker/index.php?func=detail&atid=604306&aid...
It's the result of the opposite problem from memory leaks: memory getting prematurely freed.
I know it's in the manually managed system heap (versus the garbage collector's), because the corruption is only showing up in memory allocated from the system heap.
The problem, if you can track it down, should manifest (unfortunately probably only very intermittently) as an invalid write to freed memory.
-mental