Hello
> after some extensive bug hunt last night I've tracked down the memory
> leak problem which causes V to crash quickly on AGA and a little less
> quickly on non-AGA systems -- everytime an image is resized, it
> allocates a new bitmap (resized one), but this bitmap is never freed,
> neither when the page is left, nor when V quits. On AGA, this
> bitmap will be directly in chip memory, thus fragmenting and draining
> it quickly.
Might have known it had something to do with image memory allocation! :/
>
> The bug has been fixed on the cvs tree already. Update soon ;)
Thats VERY good news!! Although my comps are not AGA anymore Voyager still crashes a
hell of a lot. Ive even found Ibrowse (demo version) to be more stable!!! (which is
saying something! ;)
Now - can you just sort out the "loading # frames....." sticky status problem please?
I like to see a nice "Ready" comment when a page has loaded - also it occasionally
makes the computer freeze up if you then try to do anything more. (at least - it DID
with the alpha...tbh I havnt had a chance to test the beta out too much with this).
TTFN
Biff.
(p.s. is it just me imagining things or has Matt taken over the bug tracking
co-ordination of V?? (maybe in co-operation). Are you doing the same for other
projects? (I assume 3.9 was handled by you m8y))
--
Bifford the Youngest
(Sam Byford)
Visit my site:
http://www.photopoetry.co.uk
ICQ: 52983236
_____________________________________________________________________
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
