On Fri, 23 Jan 2004, Chris Hawks wrote:
> With all the problems apparently from the cache getting too large, I took
> a look at constraining the cache size. Attached is a diff for your perusal
> and testing.
>
> If the storage free space is too small, cache entries are removed until
> the free space is available.
Oldest first, I assume? Or largest first? Or largest, but not very
recent, first?
> If no more cache entries remain, a cache entry is not created and
> SaveImageInStorageCache() will 'fail' and the image will remain in
> dynamic space until the viewer finishes with it and it is removed from
> memory.
Have you tested this in low memory conditions? Do you still get crashes
with memoryhog?
Could you, by the way, email me a binary with hi-res enabled (if you
can) so I can try it on my test case?
I should note that I tried to do this myself a couple of months ago, and
failed--it still crashed.
Alex
--
Dr. Alexander R. Pruss || e-mail: [EMAIL PROTECTED]
Philosophy Department || online papers and home page:
Georgetown University || www.georgetown.edu/faculty/ap85
Washington, DC 20057 ||
U.S.A. ||
-----------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
