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
checking for resources loaded that way by checking if they're on the
dynamic heap; but it actually allocates space on the storage heap, it
looks like, so I needed to return a flag as to where a given font resource
is being kept.)
I just committed fixes.
I also simplified the custom font loading code. It turns out there is no
need at all to keep a list of the custom fonts that are being
loaded. FntDefineFont() doesn't need any deallocation (and indeed for
OS4+, you can't deallocate fonts). The GrayFnt routines do need
deallocation, but it all gets done at program exit.
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
