 |
Khorlane
Beginner
Joined: 22 Nov 2000
Posts: 10
Location: USA
|
 Posted: Fri Sep 13, 2002 2:30 pm
Zoom Zoom
|
Start zMapper, load temple.mdb. Using the zoom in and zoom out buttons on the tool bar, do a max zoom in followed by a max zoom out.
I get "canvas does not allow drawing".
Pentium III 733
128mg
Intel 810e Chipset Graphics Driver
Win98
zMapper v1.10a |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Fri Sep 13, 2002 10:22 pm
|
Can you do me a favor? Go into your Start/Programs/Accessories/SystemTools and run the Resource Monitor. Let me know what your system resources are and what happens to them as your zoom in and out. Win95/98/ME have very limited system resources (128k bytes of memory, no matter how much ram you have installed) and the "canvas" error message is often associated with running out of resources.
 |
|
|
|
|
Khorlane
Beginner
Joined: 22 Nov 2000
Posts: 10
Location: USA
|
Posted: Fri Sep 13, 2002 10:59 pm
|
Before loading zMapper:
System resources: 80% free
User resources: 80% free
GDI resources: 81% free
After loading zMapper with 'temple' map:
System resources: 70% free
User resources: 75% free
GDI resources: 70% free
After clicking zoom in button once:
System resources: 61% free
User resources: 75% free
GDI resources: 61% free
After clicking zoom in button the second time:
System resources: 57% free
User resources: 75% free
GDI resources: 57% free
.... etc ....
Those %s never go back up and soon it breaks. Upon exiting zMapper, the %s return to 80% free.
The same behavior occurs when the zMapper window is minimized and then maximized multiple times. |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Sep 14, 2002 12:36 am
|
Please do Zugg one more favor, even though it shouldn't matter per se for this bug. Post your system and OS spec. For example this is related to a graphics and memory item so I would put mine as...
Win 2k Pro
Athalon 1.0G/ATI Radeon 7200
128Mb DDR
My apologies didn't see it there guess I was sucking them down faster then I thought last night. |
|
|
|
|
Castaway
GURU
Joined: 10 Oct 2000
Posts: 793
Location: Swindon, England
|
Posted: Sat Sep 14, 2002 12:38 pm
|
*lends Vijilante her glasses*
Lady C. |
|
|
|
|
Vijilante
SubAdmin
Joined: 18 Nov 2001
Posts: 5182
|
Posted: Sat Sep 14, 2002 3:15 pm
|
I ran through this test on my system and could not see any memory usage problems during it. The only odd thing I noted is that zMapper used about 18M after loading the temple.mdb. By minimizing it it drops to 700K then after restore it only climbs to 3.3M. That leads me to believe the initial splash screen and file dialog are not released from memory. Subsequently using File|Open will bring memory usage to 4M when the dialog displays and 10M after opening a file. So there is some other function there that isn't released from memory either.
I could not cause any of them to visibly leak though. |
|
|
|
|
Zugg
MASTER
Joined: 25 Sep 2000
Posts: 23379
Location: Colorado, USA
|
Posted: Sat Sep 14, 2002 5:59 pm
|
Khorlane, try going to the http://www.microsoft.com/data page and update your MDAC/ADO software to v2.5 or above. I am not able to reproduce the resource leak here either, and it might be a bug in older MDAC software.
|
|
|
|
|
Khorlane
Beginner
Joined: 22 Nov 2000
Posts: 10
Location: USA
|
Posted: Sun Sep 15, 2002 12:29 am
|
I got MDAC version 2.6, installed it, and rebooted. No change. Still chewing on the resources :(
I've tried it on two different Win98 machines, same on each. |
|
|
|
|
|
|
|
