Each object already has a pretty thorough cleanup method that's called when I'm done with it. It is true that I don't 'release' the arrays which can grow to be quite large, I just store null to ... I guess I could dimension obj.Array[1] in the cleanup. Many of the objects are reused.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Garrett Fitzgerald Sent: Tuesday, January 30, 2007 10:16 AM To: [EMAIL PROTECTED] Subject: Re: Buffer overrun On 1/30/07, Lew Schwartz <[EMAIL PROTECTED]> wrote: > I'm writing an io intensive parse/update program that has to run > non-stop 24/7. I've only been able to keep it running for 3 - 4 hrs > due to c++ buffer overrun problems. Reminds me of the memory leak > problems that we used to have under windows nt, but I don't have any > idea how to proceed. Ideas? I don't know if it will help with this particular issue, but I know there was one programmer I helped while I was in Product Support who got a crashing program to run by making sure that every possible variable was manually released at the end of its scope, instead of allowing VFP to do the automatic out-of-scope cleanup. Think that might improve things here? [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
