JVR
January 25th, 2000, 11:08 AM
Hi,
Our reporting system consists of individual VB 6 32-bit (ported from 16-bit)executables that basically query data from a database, lay it out, and print it. We use a preview form with minimal controls that include a couple of graphics controls from Graphics Server 5.10 (that we've just upgraded to 5.40), four picturebox controls, some buttons, and two scrollbars.
We have found that each run of our executables causes 75K of memory to be leaked when run on Windows 95/98. We do not see the leak in NT. The exe's do allocate more memory at run time, but frees most allocations except for 75K.
It appears that 60k is lost with just loading the form. I found this by unloading the form just after loading. I've also systematically removed each control, but it didn't seem to have a significant impact on the leak.
We use Visual Studio 6 with SP 3. Please help.
Thanks,
JVR
Our reporting system consists of individual VB 6 32-bit (ported from 16-bit)executables that basically query data from a database, lay it out, and print it. We use a preview form with minimal controls that include a couple of graphics controls from Graphics Server 5.10 (that we've just upgraded to 5.40), four picturebox controls, some buttons, and two scrollbars.
We have found that each run of our executables causes 75K of memory to be leaked when run on Windows 95/98. We do not see the leak in NT. The exe's do allocate more memory at run time, but frees most allocations except for 75K.
It appears that 60k is lost with just loading the form. I found this by unloading the form just after loading. I've also systematically removed each control, but it didn't seem to have a significant impact on the leak.
We use Visual Studio 6 with SP 3. Please help.
Thanks,
JVR