Ibrowse & jpegtmp?huh

[Damion]

>then you might start having a problem if all
>your memory has been used for swap files

Except that this never happens. The memory is
only occupied  temporarily. After progressively
loading about 50 different jpegs with IBrowse,
the most I lost at one time was about 1.5MB
(and I suspect this was mostly memory needed
for display purposes). It's just a small area
of memory that is used (and reused) for decoding.

(edit) The memory - slider (for jpegtemp in
Ibrowse) only adjusts the amount of memory that
can be used within "jpegtemp" to decode. So
you could set it to a small amount if you only
had a small amount of fastram (slightly slower
decoding speeds) or higher/off with more
fastram (slightly faster decoding speeds).
The memory is returned after use, and in my
experience rarely is <2mb used at once.

[carls]

Oops.
Again, I'm sorry for my smarty-pants attitude in my previous posts.

[lurkist]

Yes, there seems to be some confusion - Jpegtmp: is not the same as the Ibrowse cache, Jpegtmp can safely be assigned to ram and do its own thing in the background, all files and cookies will still be saved to the cache (permanently if your cache is on HD)

"IB cache is responsible for 90% of crashes"

Agreed.