The workround that I've used is to employ the Windows API - it IS the MapInfo session and not the MBX that has the leak. As Peter says you only get the memory back when you shut MI Pro.
I'm working from VB and trying to get a grab of the map to put up on screen during processing - I used a modified version of the code at this link - http://support.microsoft.com/default.aspx?scid=KB;en-us;q161299 Theres a lot of declarations to modify to put it into an MBX so if this is along the lines you want then pehaps a VB process with a DDE link? HTH Paul Crisp Syntegra Innovation Place Delta Bank Road Newcastle NE11 9DJ Tel 0191 461 4522 Fax 0191 460 1987 -----Original Message----- From: Peter Horsboll Moller [mailto:[EMAIL PROTECTED]] Sent: 17 December 2002 08:26 To: 'Carl Brenner ' Cc: '[EMAIL PROTECTED]' Subject: RE: MI-L Save Window Memory Leak Didn't they fix this bug with the MapInfo 7.0.0.26 patch they released shortly after the release of MapInfo 7.0 ? I'm not sure you'll fix the problem by splitting your MapBasic applications, but this might of cause depend of the way this Memory leak works. My experience tells me that if there is a memory leak somewhere in MapInfo then it is connected to MapInfo and not the MapBasic application. So the memory will not be released before MapInfo is ?closed. Closing the MapBasic application will not free the used memory. So if this is true the way to come around this problem would be to start a new instance of MapInfo, maybe with a simple MapBasic application, and let this instance do the memory heavy work. When the work is done, close that MapInfo and open another if nessessary. Peter Horsboll Moller GIS Developer COWI A/S Rugardsvej 55 DK 5000 Odense C Tel +45 6313 5013 Direct +45 6313 5008 Mobil +45 2270 4308 Fax +45 6313 5090 Kampsax blev i juni 2002 overtaget af COWI. I forbindelse med den igangvaerende integrationsprocess udskiftes vores Kampsax e-mail adresser med COWI e-mail adresser.Hjemmesideadresser forbliver uaendrede -----Original Message----- From: Carl Brenner To: [EMAIL PROTECTED] Sent: 16-12-02 19:16 Subject: MI-L Save Window Memory Leak Within MapBasic 7, when you use the Save Window command, a memory leak exists. MapInfo knows about it - Bug # 24674 - I'm curious if anyone has a clever workaround for it. The only thing I can think of is to split the work into separate MapBasic programs. Thanks! _________________________________________________________________ The new MSN 8: smart spam protection and 2 months FREE* http://join.msn.com/?page=features/junkmail --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 4563 --------------------------------------------------------------------- List hosting provided by Directions Magazine | www.directionsmag.com | To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Message number: 4568 ******************************************************************** This email may contain information which is privileged or confidential. If you are not the intended recipient of this email, please notify the sender immediately and delete it without reading, copying, storing, forwarding or disclosing its contents to any other person Thank you Check us out at http://www.syntegra.com ********************************************************************
