| Geoff Wass [dBVIPS] 2007-01-13, 7:18 am |
| In article <#6k5ZvnNHHA.1068@news-server>, dennis8706@verizon.net=20
says...
> We suspect that possibly the print preview screen leaks memory when our=
=20
> program goes in and out of it often. We would like some comments on this=
=20
> possibility from all of you.
> Dennis and Maxine
>=20
Dennis & Maxime,
Just a thought... use MEMORY() before and after previewing and call=20
previewing a large number of times. There are going to be slight=20
variations in the numbers MEMORY() gives you simply because of the way=20
Windows manages memory, but if you see a trend of significant general=20
decline in values you have a pretty good case for a leak. I have used=20
this technique to narrow down to a single like of code where something=20
is leaking.
You can use ? MEMORY() and SET ALTERNATE ON/OFF, plus SET ALTERNATE TO=20
to save the output to a text file for later analysis.
--=20
Geoff Wass [dBVIPS]
Montr=E9al, Qu=E9bec, Canada
..|.|.| dBASE info at http://geocities.com/geoff_wass |.|.|.
..|.|.| ---------------------------------------------------------- |.|.|.
..|.|.| IT Consultant http://Geoff_Wass.com |.|.|.
|