>V gives back the ram too but it uses some libraries (ssl, image >decoders, about screen, MUI classes) which don't give back the memory. >They stay in ram until more memory is needed, type 'avail flush' in >a shell after exiting V to find out. Well something is definitely not working right (latest beta 95). V is using up huge amounts of RAM and running out of it very quickly, until it stops displaying images altogether (I think it says 'No memory for bitmap'). It is just happening a lot faster now that people like me are running V on 16 or 32bit Workbench screens. And AFAIK there is no way no free the memory (flush cache options don't work) without quiting. Why do the image decoders allocate way more memory than I have set in the V's memory cache preference option anyway? (if I set it to 8Mb, then that's more or less all the RAM I'd expect V to allocate in one session, not 25Mb!) Anyway, its not the end of the world, maybe its already fixed in a newer revision. Gaven _____________________________________________________________________ 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
