FastMM

Exceptions raised by the memory manager vary from an access violation (for block corruptions) or an EOutOfMemory exception (for out of memory situations). Unfortunately I don't know what other advice to give you.

FastMM (which is basically the same as the default memory manager) is used in many production multi-threaded applications so I am still doubtful that it is a problem in the memory manager - if there was such a problem I would have received more similar reports. Others that I have received in the past almost always turned out to be bugs in user code, and those that were not (we're talking long ago here) have been fixed.