Comment #24 on issue 2335 by d...@gnu.org: 64 bit LilyPond segfaults http://code.google.com/p/lilypond/issues/detail?id=2335
From Scheme, you can't really do much of hacking smobs and memory management. It is likely that anything you can do to make the problem disappear is more related to garbage collection running at a different time rather than a direct consequence of the outcommented stuff.
Does not harm to try, but I would not assign all too much importance to the results. Except that it is conceivable that some code in LilyPond might have been written on fragile assumptions regarding when objects will no longer be accessed.
But I would not hold my breath for that. _______________________________________________ bug-lilypond mailing list bug-lilypond@gnu.org https://lists.gnu.org/mailman/listinfo/bug-lilypond
