Hi Gaven
Gaven Eogan wrote:
> I've noticed that the latest 3.3.95 (and previous) V3's hold on to memory
> allocated to images loaded until the program is shutdown. It just eats up
> all memory until there is none left and then it can't display any more
> images. Flushing the caches doesn't do anything, and neither does going
> back in the history to try and get V to drop images in 'forward' history.
> This is probably not as noticable for low-depth screens but on 32-bit
> Voodoo3 displays, memory is eaten up in megabytes per image! (And yes it
> appears to allocate twice the memory compared to opening the same image
> when V is on a 16-bit screen). When I start V there is usually about 20Mb
> free but this goes down to nothing in less than half an hour. For the
> moment I've had to revert Workbench back to 16-bit to slow down the
> problem. Is V supposed to hold onto all allocated image memory until
> shutdown, or when should it free it?
It happens only on a few sites, I'm still using 3.2.13 as more stable
version.
AMIcably
A.Varamogianis
--
<tsb> Athanassios Varamogianis [EMAIL PROTECTED] Hellas(Greece)
<sb> Director,Videographer,Photographer,Video Editor
<sb>Amiga 4000 060/50,OV,VLM,VLG
<tsb>*#Team Amiga#* and #*C.U.C.U.G Member#*
_____________________________________________________________________
Voyager Mailing List - http://v3.vapor.com/
Voyager FAQ....: http://faq.vapor.com/voyager/
Listserver Help: mailto:[EMAIL PROTECTED]?Subject=HELP
Unsubscribe....: mailto:[EMAIL PROTECTED]?Subject=UNSUBSCRIBE
