|
From: | Ben |
Subject: | Re: LilyPond can't engrave 16 pages of music |
Date: | Fri, 21 Dec 2018 20:45:09 -0500 |
User-agent: | Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.3.3 |
On 12/21/2018 7:46 PM, Thomas Morley
wrote:
Am Sa., 22. Dez. 2018 um 00:48 Uhr schrieb Reggie <address@hidden>:I am trying to understand theoretically why this is failing. It's only 16 pages. I am a minimalist composer so as a test I tried this extreme situation. But yet I don't quite agree rather that it's that extreme. It's only 16 pages and LilyPond crashes. \version "2.19.82" { \time 4/4 \repeat unfold 1000 { c4 d e f } % TEN PAGES of music \repeat unfold 1000 { f1 } % + SIX MORE PAGES of music \repeat unfold 1000 { c4 d e f } % BUT WHEN ADDING MORE PAGES, fail NOW } wHY? Preprocessing graphical objects...terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Exited with return code 6.Works here, returning a 25-pages pdf. I'm on Ubuntu-18.04 64-bit Cheers, Harm _______________________________________________ lilypond-user mailing list address@hidden https://lists.gnu.org/mailman/listinfo/lilypond-user
Harm, What are your system specs? I can compile the file on my Linux Mint x64 laptop with 16GB of RAM, rockin' an 8th gen i7 but it took about 10 minutes almost. That seems very very slow. Did you experience the same wait times? On Windows 10 x64 it flat out crashed, with a different error code number but the same family of crash I believe... Preprocessing graphical objects...terminate called after throwing an instance of 'std::bad_alloc' what(): std::bad_alloc Exited with return code 3.
|
[Prev in Thread] | Current Thread | [Next in Thread] |