On Sun, 01 Aug 1999 06:10:34 -0500, Michael E. Thompson RN wrote:
> On 30-Jul-99, Willi Burkhardt wrote:
> > Hi all,
> > V3 seems to crash very often in low memory situations. Usually it's the
> > image decoder Process. If I switch off image-loading V3 is much more stable!
> > V-2.95 used to be the same!
> > How much memory do you have on your machines?
> > Does anyone run V3 on a ECS-Screen?
>
>
> I have gone from a 24 bit screen down to a 16 and then to an 8 bit screen
> attempting to decrease the number of crashes caused by V3 and V2.9.
>
> Go to a chat room on Yahoo, and let it run for 30-45 min. Guarenteed crash!
Voyager 2.95 has a problem with its caching routines: No matter what
limits (either for disk or memory) you set in Preferences, V ignores
them, and just uses most all available memory, particularly if you use
multiple windows. Each window gets its own memory cache, I believe.
On my 3000/25 2/16 megs, it doesn't take long with 4 to 6 windows to
use up all but about 500K of FAST RAM. I have a 4 meg graphics card,
so that keeps my CHIP RAM from being used too much. Flushing the
image and document memory caches a lot seems the only solution.
--
Patrick Bartek (NoLife Polymath Group)
[EMAIL PROTECTED]
http://www.access1.net/bartek
____________________________________________________________
Voyager Mailing List - Info & Archive: http://www.vapor.com/
For Listserver Help: <[EMAIL PROTECTED]>, "HELP"
To Unsubscribe: <[EMAIL PROTECTED]>, "UNSUBSCRIBE"
