At 9:16 AM -0700 8/22/00, Rich Morin wrote: >At 11:08 PM -0600 8/20/00, Joseph A. DiVerdi wrote: >>Unfortunately, there is a memory leak somewhere ... > >As I understand it, there are several kinds of possible memory leaks: > >* MacPerl is simply broken > >* Your script is allocating stuff, but not releasing it > >* Your script is creating circular references, which Perl's GC is > unable to resolve. > >Of course, when I say "your script", this includes any other code >you're linking in. > >One interesting test would involve: > >* putting the entire mainline code into a "for (;;) {}" block > >* putting every global variable you can find into a "my", > just within the block > >* having the mainline code terminate every so often, falling > back into the "for (;;) {}" block and recycling > >I suspect that there may be a way for a MacPerl program to find >out how much memory it has left. Perhaps Matthias or Chris can >tell us how to do that? Dear Rich, Thanks for your response. I understand the cause of the memory leak. It's been traced down to the MacPerl interface to "loaded" XCMDs and XFCNs. I sent a bug report with supporting bits to Matthias some time ago so he's aware of the problem. It's my expectation that this problem is not high on the priority list (admittedly it's my supposition but no one has disabused me of it) so I am forced to look for work around solutions while I ponder the real one. At this time I am forced to "quit script" day and restart the script once every calendar. That's my current work around. I'd like to automate that work around by automatically quitting the script perhaps by sending a "cmd-." to it/MacPerl using Cron. Best regards, Joseph -- Joseph A. DiVerdi, Ph.D., M.B.A. <mailto:diverdi@XTRsystems.com> 970.221.3982 (voice) <http://www.XTRsystems.com> 970.224.3723 (fax) %PGPKeyID=('D50A9E33') # ===== Want to unsubscribe from this list? # ===== Send mail with body "unsubscribe" to macperl-request@macperl.org