On 12/28/05, Jorrit Tyberghein <[EMAIL PROTECTED]> wrote: > The idea is that the block allocator should be empty at the time it is > destructed. When this problem manifests itself it means there is a > leak elsewhere in the engine (for example if the objects in that > kdtree are leaking). > So the proper fix for this problem is to fix the leak.
Not in this case. You're mis-interpreting this particular crash. If you look back at the original message, you will see that it was trying to delete an object from the block-allocator which had already been deleted from the allocator. This goes along with what Peter was saying. -- ES ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://ads.osdn.com/?ad_idv37&alloc_id865&op=click _______________________________________________ Crystal-main mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/crystal-main Unsubscribe: mailto:[EMAIL PROTECTED]
