Hi there, Is there anyone on this list who would be willing to help this bug along? I will gladly pay for this feature to be working again might any of you be interested. I have 9 full orchestra+chorus projects to render by… well its already in rehearsal :) and most of them displays the bug.
tl,dr; LilyPond core dumps it seems in the ly:page-turn-breaking algorithm. Following is my post on the lilypond-bug mailing list from this February first. Le sam. 1 févr. 2020 à 09:46, Pierre-Luc Gauthier <[email protected]> a écrit : > So, this problem comes up once in awhile but, I do not know why, its > now recurrent on multiple projects now. > All my orchestral projects compile about 96 PDF all using the > ly:page-turn-breaking algorithm that I love so very very much. But > sometimes, it fails with the error bellow. By sometimes I mean, it > *always* breaks until I do significant music changes that, I suppose, > changes the page layout until the problem is avoided by chance. > > Here is the interesting tail of the output : > > Calculating page and line breaks (8 possible page breaks)...lilypond: > /tmp/packerbuild-1000/lilypond-git/lilypond-git/src/lilypond/lily/page-turn-page-breaking.cc:218: > void Page_turn_page_breaking::calc_subproblem(vsize): Assertion > `!std::isinf (best.demerits_) && start < end - 1' failed. > ./publish.sh: line 11: 63598 Aborted (core dumped) > lilypond -dno-point-and-click -ddelete-intermediate-files > -dembed-source-code --pdf -o ./upload/ ./parts-book-template.ily > > I'm sure there is a way to create a MWE but I've never manage to do > so. It's sort of a "once in a specific while" kind of problem. > > How can I help this bug along? Le sam. 1 févr. 2020 à 09:54, Thomas Morley <[email protected]> a écrit : > This may be related to https://sourceforge.net/p/testlilyissues/issues/4943/ Pierre-Luc Gauthier <[email protected]> writes: > g++ --verbose > returns : > Target: x86_64-pc-linux-gnu > Le sam. 1 févr. 2020 à 11:05, David Kastrup <[email protected]> a écrit : > > 64bit. Should not be affected by the bug Harm mentioned. Le sam. 1 févr. 2020 à 12:59, Pierre-Luc Gauthier <[email protected]> a écrit : > Should I provide anything more helpful to help advance an eventual issue ? The problem being very hard to reproduce and I have this very quirky system of compiling parts so, I suppose I will have to provide a whole project that displays the problem to the person interested in this issue? Thanks in advance. -- Pierre-Luc Gauthier
