[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMu

From: David Kastrup
Subject: Re: Issue 2067 in lilypond: Patch: Give \displayLilyMusic and \displayMusic optional port arguments.
Date: Mon, 05 Dec 2011 14:05:16 +0100
User-agent: Gnus/5.13 (Gnus v5.13) Emacs/24.0.90 (gnu/linux)

address@hidden writes:

> Updates:
>       Labels: -Patch-review Patch-new
> Comment #13 on issue 2067 by address@hidden: Patch: Give
> \displayLilyMusic and \displayMusic optional port arguments.
> http://code.google.com/p/lilypond/issues/detail?id=2067
> There was no change in the regtest logs between current master and
> master + this patch.  If a "parsed objects should be dead" was already
> added, that's not Patchy's concern.
> ... oh wait, is this some silly --no-optimize thing?  Nobody has added
> that to Patchy's instructions, so maybe he missed some such error.  I
> guess I should recheck.

In my opinion, Patchy should use -ddebug-gc-assert-parsed-dead by
default.  Apparently the dirt is already in current master (and should
be bisected and the culprit reverted), but it is definitely a bad idea
to omit this test when autochecking.

People with multigigabyte 64bit machines might shrug memory leaks off,
but for something like running large builds or regtests, it is not funny
when the memory requirements keep growing during a multi-source run.

Not to mention that this stuff can also cause crashes and Heisenbugs.

David Kastrup

reply via email to

[Prev in Thread] Current Thread [Next in Thread]