> Is there any hope of Voyager's memory leak problem being fixed anytime
> soon? I can open V with having 1.4MB of chip ram, and after I've shut
> it down I have like 0.8MB chip ram anymore even though I've started
> no other programs and V is shut down already. This means I have to
> reboot the computer after 4-5 times of using V3.3. This problem was
> not present in 3.2. Any chance of getting it removed again? It's
> really annoying.
As far as I recall there is no memory leak..
If you are running out of chipram it is probably because V allocates a
fair few bitmaps (the main document bitmap for instance) with the flag
BMF_DISPLAYABLE - these *will* go into chipram and things like FBlit
aren't allowed to promote them. FScreen will though, you might want to
try it. I seem to remember it worked very well for me and others have
had good experiences once V is taking bitmaps from fastram..
If V is fragmenting chip ram (when you quit you only have a very small
"largest block" left) then I have no idea how we'd solve this..
--
Matt
_____________________________________________________________________
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
