[SOLVED] Version 1.2.4 LeakView problem?

[Gary Randall]

I've been using Leak View successfully.  I output to a log file and only look at once in a while, when revisions aren't working quite right.  Lately I've been getting the following:

Error while parsing trace file.

Total Mem allocated: 8526841939240609676
Leaking Mem Size: 7331487662766124369
Leaking Blocks Count: 8304836264914369809

My program has a number of forms which are all created and freed in try-finally constructs.  Just opening the main form produced the above error.  I've been steadily adding to the program and haven't seen any errors that made me suspect memory leaks.  It's probably been over a month since I resolved a couple of leaks.  I believe I installed the new Lazarus version 1.2.4 sometime right after it was released, after Nov. 11, 2014.  I don't see how the program could even run with memory leaks like that.  Is it possible the new version isn't working, or maybe installed wrong?  It appears the trace file is corrupted.

Gary

[Gary Randall]

Well, I'm embarrassed.  Mark it up to short term memory loss.  I discovered that I was running Leak View on an empty heap.trc file.  I wasn't closing the running program correctly, just interrupting it by clicking on the "Stop" icon to return to the IDE.  Very nice procedure I discovered recently for quick testing,  but apparently doesn't close/write the heap.trc file.    Once I closed it by exiting the main form Leap View reported correctly and I had no leaks.

Gary