Re: Manual page breaking causing assertion failure

[Carl Sorensen]

On 7/21/16 11:41 AM, "Chris Yate" <address@hidden> wrote:

>Hey Abraham / BugsList people,
>
>I'm guessing nobody had a chance to look at this problem. I'm experiencing
>it again, and it's really slowing me down.
>
>Is there anything else I can do to help debug / isolate the issue? It's
>still there in 2.19.45 but I guess we'd expect that anyway.
>
>Chris
>
>On Sat, 9 Jan 2016 at 09:55 Chris Yate <address@hidden> wrote:
>
>> So, it turns out this was easy to minimise the code. File is attached.
>> It's still ~70 bars but only one voice, which is the dynamics staff of a
>> piano score (without anything else), so it's only silent music.
>>
>> "AutoPageBreaksOff" in the score block causes the exception failure.
>>
>> I note some "insane spring distance" warnings.These don't happen in the
>> real thing.

I suspect you have not yet created a LilyPond "Tiny Example".

http://lilypond.org/tiny-examples.html

While you have greatly reduced the file from the original size, there's
still a lot of stuff in there that I doubt is necessary to trigger the
assertion failure.

For example, the piece starts with a \partial.  Does the error still occur
without the \partial?  If so, take it out.

Similarly, there are lots of dynamic indications in the part.  Can any of
them be removed and still have the assertion failure?  if so, take them
out.

It would be much nicer if you could write the code something like

\repeat unfold 20 s2.
\crescTextCresc s8\cresc s4\! s4. |
\repeat unfold 50 s2.

so that we would know the following:

a) What minimum set of dynamics causes the assertion failure
b) How many bars are necessary to cause the assertion failure

Because few of the developers work in Windows, it will be difficult for
them to debug this problem.  So anything you can do to narrow it down will
increase the likelihood that the problem will be solved.

Thanks,

Carl