I have a complex application that works as expected when compiled normally, but closing a form generates an access violation when compiled using FastMM 4.97 (the latest).The AV occurs when the message
I checked the FastMM4 with D6. When I debug a simple application with uses \"Forms\", I everytime got 3 lines f开发者_运维百科or memory leak.
I have seen recently a strange behavior in my program. After creating large amounts of objects (500MB of RAM) then releasing them, the program\'s memory footprint does not return to its original size.
In a recent post ( My program never releases the memory back. Why? ) I show that when using FastMM, the application does not release substantial amounts of memory back to the system.
This is from a custom namespacer handler done in Delphi I use to load files into a webbrowser component.
I have been using FastMM4 version 4.92 in my Delphi 6 Pro application smoothly.I now want to use it in a package I created (BPL).I tried putting the units in the Contains section and then moving them
Is it possible to think to have in future an automatic garbage collector in Delphi? There are many applicat开发者_JAVA百科ions in which a higly detailed control on when to free an object is not so imp
I want to build a DLL that exports functions that return a string. This DLL should work with other programming languages!!
I\'d like to get FastMM memory leak report that shows up on app shutdown, but in a file instead of the dialog box. The idea is 开发者_开发技巧to use it in a release build as I have trouble reproducing
I tested my application with FastMM and FullDebugMode turned on, since I had some shutdown problems. Afte开发者_开发技巧r solving bunch of my own problems FastMM started to complain about calling vir