|
From: | lilypond |
Subject: | Re: Issue 2356 in lilypond: Lilypond segfaults |
Date: | Sat, 03 Mar 2012 15:26:04 +0000 |
Comment #21 on issue 2356 by address@hidden: Lilypond segfaults http://code.google.com/p/lilypond/issues/detail?id=2356"protecting" is an operation with permanent performance and memory impact during the life time of protection, so it is a bad idea to do it in situations where the pairing is not guaranteed (like in constructor/destructor pairs). If contexts need to be kept alive for some engraver or other entity, the way to do that is to mark them during the gc mark phase.
So this "fix" definitely looks wrong. If you can trace the problem to premature collection of a context, that is where we need to look.
[Prev in Thread] | Current Thread | [Next in Thread] |