I committed a rudimentary fix, which seems to fix bug #665, but at the cost
of not displaying images once memory has run out. It really ought to be
reclaiming cache memory when it's running out.
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online papers and home page: www.georgetown.edu/faculty/ap85
--------------------------------------------------------------------------
"Philosophiam discimus non ut tantum sciamus, sed ut boni efficiamur."
- Paul of Worczyn (1424)
----- Original Message -----
From: "Alexander R. Pruss" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Monday, September 15, 2003 8:36 AM
Subject: cache allocation
> AllocateCacheRecord() fails to check if the new record insertion worked.
> SaveImageInStorageCache() then writes to the record, even if
> AllocateCacheRecord() returned a NULL handle. I don't know enough about
the
> cache code to want to fix it myself. This may be related to bug #665.
> --
> Dr. Alexander R. Pruss
> Department of Philosophy
> Georgetown University
> Washington, DC 20057-1133 U.S.A.
> e-mail: [EMAIL PROTECTED]
> online papers and home page: www.georgetown.edu/faculty/ap85
> --------------------------------------------------------------------------
> "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
>
_______________________________________________
plucker-dev mailing list
[EMAIL PROTECTED]
http://lists.rubberchicken.org/mailman/listinfo/plucker-dev
