Han-Wen Nienhuys wrote:
I'm not convinced that you have fixed the original problem. I've CVS
upped GUILE, and now LilyPond is again soaring to 750mb memory
footprints while processing many trivial files. The problem is a little
more acute, since I've upped the GC yield for performance reasons.
And... this version of Lily even has the kludge I built for 1.6: ie.
clearing the 'module property, and replacing scm_stand_in_procs with a
weak key hash table.
Paint my face in fluorescent blushing red. This leak was actually caused
by me forgetting to #define MODULE_GC_KLUDGE. Case closed, I hope!
--
Han-Wen Nienhuys - [EMAIL PROTECTED] - http://www.xs4all.nl/~hanwen
_______________________________________________
Guile-devel mailing list
Guile-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/guile-devel
