I have a bug that is quite reproducible in build 439, that is probably something to do with threads/timing.
I have a single-core CPU (Pentium4), with another process running to consume 100% CPU, I open Cirrus to view changes in a file (via Code Co-op), then press ESC to close Cirrus. Most of the time, I get a warning message box saying:
"This application has leaked memory. The small block leaks are (excluding expected leaks registered by pointer):
21-28 bytes: TAutoCompleteURLFilter x 1"
Then on OKing this, I get another message box:
"FastMM has detected a FreeMem call after FastMM was uninstalled"
Then, after OKing this, I get:
"Runtime error 204 at 004049E5".
I have a single-core CPU (Pentium4), with another process running to consume 100% CPU, I open Cirrus to view changes in a file (via Code Co-op), then press ESC to close Cirrus. Most of the time, I get a warning message box saying:
"This application has leaked memory. The small block leaks are (excluding expected leaks registered by pointer):
21-28 bytes: TAutoCompleteURLFilter x 1"
Then on OKing this, I get another message box:
"FastMM has detected a FreeMem call after FastMM was uninstalled"
Then, after OKing this, I get:
"Runtime error 204 at 004049E5".
Comment