To be honest, I had been hoping for something more helpful. Because it's not immediately obvious to me how to go about tracking down a memory leak in any one of a few dozen components on IDE shutdown without just eyeballing the code, which I would think would take a prohibitive amount of time, compared to me just using Task Manager to blow away the IDE process when it happens.
I've been a Delphi dev since Delphi 1, and I'd like to think I've a reasonable idea how to write clean, safe Delphi code myself, but job-inherited/otherwise acquired components loaded into the IDE is another thing. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Phil Scadden > Do you have any tips/pointers on tracking down this shutdown issues? > I agree that it's most likely our own components that are causing > these errors for me; just wondered if you have any general suggestions > about solving them. Yes. If its not memory leaks then what other sin does a component commit that results in this behaviour. _______________________________________________ NZ Borland Developers Group - Delphi mailing list Post: delphi@delphi.org.nz Admin: http://delphi.org.nz/mailman/listinfo/delphi Unsubscribe: send an email to [EMAIL PROTECTED] with Subject: unsubscribe
