In July last year I logged a problem with MI Support re a memory leak in =
6.5 that had persisted from 6.0. The problem is caused by an INSERT =
statement issued from the MI, MapBasic window or a MapBasic program. The =
INSERT leaks memory at about 210 bytes per call (consistent with your =
loop).=20
Problem is that if you are doing large volume of inserts it is a =
nuisance. If v. large then you get virtual memory out messages. Others =
have noted the same problem during last year. Is not fixed by closing =
tables, or restarting application. Quit MI and mem is recovered.
I sent MI support a test program but they were unable to reproduce on =
their environment. Mine is a Dell, PII, 333Mhz,128Mb notebook with
NT 4.0 sp 6a. Have run on a Win98 system without the same problem.
I thought that the latest MI patch (6.5.0.3100 ) might have fixed in =
spite of the elusive language in the "maintenance read me" ...
"17865 A memory issue arose when running certain MapBasic programs that =
contained specific coding scenarios. This has been corrected." Have to =
be grateful for some information!
Have just retested the patched version and the problem is not resolved. =
I suppose it is reasonable that a problem of this sort can be =
hardware/OS induced, but considering it was not there in 5.5 but was in =
6.0 and involves 1 statement, you'd think it could be fixed.
My solution is to keep the last most reliable version for those heavy =
number crunching jobs (I keep 5.5), or run on a PC which doesnt show the =
problem.
Hate to think of the amount of time spent on this in isolating a line of =
code in an application - you always suspect dodgy programming first of =
course.
Phil.
----- Original Message -----=20
From: "Taylor, Michael Graham" <[EMAIL PROTECTED]>
To: "Mapinfo List" <[EMAIL PROTECTED]>
Sent: Thursday, January 10, 2002 10:42 AM
Subject: MI-L MI 6.5 Leaky?
> Hi
>=20
> Recently I've noticed that MI 6.5 (NT) appears to leak memory when
> certain mapbasic routines are run. I've finally got around to having =
a
> bit of a look at it and this i what I have found. The following =
program
> causes my memory usage to go from=20
> 118892 to 125464
> This is not released once the program has finished but is released =
when
> MI is exitted.
> The table is approx 33000 polygons
>=20
> fetch first from parcel
> do until EOT(parcel)
> fetch next from parcel
> loop
>=20
> Adding in a create and insert command as follows caused twice the leak
>=20
> create table myTemp (id integer)
> fetch first from parcel
> do until EOT(parcel)
> fetch next from parcel
> insert into mytemp (id) values (1)
> loop
>=20
> I am running MI6.5 on a Dell Precision 220 NT4.5
> Is this something to do with my system or are others able to duplicate
> it?
>=20
> --=20
> Mike Taylor
> ______________________________________________=20
> GIS Senior Consultant mailto:[EMAIL PROTECTED]=20
> Sinclair Knight Merz Limited http:\\www.skmconsulting.com=20
> Level 12, Mayfair House Tel: +64 4 473 4265=20
> 54 The Terrace Fax: +64 4 473 3369
> PO Box 10283,Wellington
> New Zealand
>=20
>=20
>=20
> =
_______________________________________________________________________
> List hosting provided by Directions Magazine | www.directionsmag.com |
> To unsubscribe, send e-mail to [EMAIL PROTECTED] and
> put "unsubscribe MapInfo-L" in the message body.=20
_______________________________________________________________________
List hosting provided by Directions Magazine | www.directionsmag.com |
To unsubscribe, send e-mail to [EMAIL PROTECTED] and
put "unsubscribe MapInfo-L" in the message body.
