On Fri, 12 Dec 2003 at 19:50, Alexander R. Pruss wrote:
I can't duplicate all of your memory leaks. But I've found two memory
leaks, one of which was a really bad one on which all of the data loaded
from VFS fonts was not being returned to the system. (I was assuming that
On Mon, 15 Dec 2003, Alan Hoyle wrote:
With the CVS from yesterday, I get a Free Handle crash on entry into
Plucker. If I copy my favorite custom font back into main memory, I don't
get the crash anymore.
Hmm. Try deleting the Plucker font cache file from RAM with
Filez/Cliefiles/whatever
On Mon, 15 Dec 2003, Alan Hoyle wrote:
With the CVS from yesterday, I get a Free Handle crash on entry into
Plucker. If I copy my favorite custom font back into main memory, I don't
get the crash anymore.
Let me know if this is still happening with the current CVS code. Also,
please let me
On Mon, 15 Dec 2003 at 10:12, Alexander R. Pruss wrote:
On Mon, 15 Dec 2003, Alan Hoyle wrote:
With the CVS from yesterday, I get a Free Handle crash on entry into
Plucker. If I copy my favorite custom font back into main memory, I don't
get the crash anymore.
Hmm. Try deleting the
On Mon, 15 Dec 2003 at 10:20, Alexander R. Pruss wrote:
On Mon, 15 Dec 2003, Alan Hoyle wrote:
With the CVS from yesterday, I get a Free Handle crash on entry into
Plucker. If I copy my favorite custom font back into main memory, I don't
get the crash anymore.
Let me know if this is
There were a bunch of bugs in the vfs font caching code, and I fixed them
this morning. Unfortunately, none of the bugs looked to me like they would
give that kind of an error message. But who knows?
By the way, something I found useful is to set a very small font for the
library and a larger
On Fri, 12 Dec 2003 at 09:40, Alexander R. Pruss wrote:
Subject says it all. Just drop filename.prc into any of the Plucker
directories on VFS. Alex
I don't know that these two are necessarily correlated, but the latest
CVS development snapshot has a serious memory leak.
-alan
--
Alan
On Fri, 12 Dec 2003, Alan Hoyle wrote:
On Fri, 12 Dec 2003 at 09:40, Alexander R. Pruss wrote:
Subject says it all. Just drop filename.prc into any of the Plucker
directories on VFS. Alex
I don't know that these two are necessarily correlated, but the latest
CVS development snapshot has
On Fri, 12 Dec 2003 at 15:56, Alexander R. Pruss wrote:
On Fri, 12 Dec 2003, Alan Hoyle wrote:
On Fri, 12 Dec 2003 at 09:40, Alexander R. Pruss wrote:
Subject says it all. Just drop filename.prc into any of the Plucker
directories on VFS. Alex
I don't know that these two are
On Fri, 12 Dec 2003, Alan Hoyle wrote:
Behavior on my T|T:
1. Do warm reset.
2. Go to ZLauncher. Reports 5590K free
3. Hit Plucker button. library comes up: font previously selected is
smallest built-in.
4. Return to ZLauncher. Reports 5544K free (delta: -46K)
5. Hit plucker
I can't duplicate all of your memory leaks. But I've found two memory
leaks, one of which was a really bad one on which all of the data loaded
from VFS fonts was not being returned to the system. (I was assuming that
VFSFileDBGetResource() allocates space on the dynamic heap, and so I was
From: Michael Nordstrom [EMAIL PROTECTED]
On Wed, Dec 03, 2003, Alexander R. Pruss wrote:
thing I could do is additionally store in the prefs a small cache
of the pathnames and volumeRefs of the last three,
I don't think it's a good idea to store the volumeRefs; it's safer
to store
I think I'm going to add VFS font support. A full anti-aliased font package
can be enormous. It should be pretty easy to add the support. Any
thoughts?
--
Dr. Alexander R. Pruss
Department of Philosophy
Georgetown University
Washington, DC 20057-1133 U.S.A.
e-mail: [EMAIL PROTECTED]
online
Alexander R. Pruss wrote:
I think I'm going to add VFS font support. A full anti-aliased font package
can be enormous. It should be pretty easy to add the support. Any
thoughts?
--
Sounds like a good idea, if compactness can be done. I put some aa fonts
on my T|T device this past week
Here are some thoughts. Scanning for fonts on VFS is time consuming. One
could do it with no real extra time penalty, however, if one did it at the
same time as scanning VFS for Plucker documents. But such scanning doesn't
always happen--it only happens when one is in the library, and not
On Wed, Dec 03, 2003, Alexander R. Pruss wrote:
thing I could do is additionally store in the prefs a small cache
of the pathnames and volumeRefs of the last three,
I don't think it's a good idea to store the volumeRefs; it's safer
to store the volume label and then get the volumeRef using
16 matches
Mail list logo
