Here is a PM received regarding memory leaks that may be of interest to users:
Wednesday, October 10, 2001 7:37 PM ET
To: Nick Morvay
From: Gerry R
Nick,
I came across this post of yours regarding memory usage in the CSW ticker, a couple of points. The memory the Ticker uses is managed by the Java VM. The Netscape VM does not recycle memory properly, the one that come with Microsoft's IE does a pretty good job. Opening a Java console and typing 'm' in it will display the memory currently being used. As the Ticker collects trades it will use more memory.
To release the memory being used, do not reboot. If you close all of your browser windows that will terminate the Java VM, and free any memory being used.
Thanks,
Gerry Rempel
Stockwatch Java Team
---------
Message #12613 from Nick Morvay at Sep 7, 2001 6:45 PM
I've noticed similar memory usage when using CSW java screens. Although I have not verified this, it seems these are memory leak problems. In fact, if I keep opening and closing a LOT of java screens on 4 monitors throughout the day, even my dual 1Ghz P3 system with 1GB RAM will eventually become noticeably sluggish. Go figure!
I have not tried this, but instead of rebooting try logging in again. I'm not sure but Windows may clear or release the user memory space at that time. I've also noticed that Win2k seems to handle memory problems much better than Win98.
The hardware requirements for XP is the same as for Win2K. The P3-600/512RAM should do the job well.
A caution on XP upgrade. From news groups I've read (no first hand experience) when you change any hardware or drivers on the WinXP system it will need to be re-enabled by calling MS for a key. I'm holding at Win2k. FWIW
Regards,
Nick |
