Re: Fwd: Compile crashing... help!

2018-05-11 Thread Aaron Hill 

On 2018-05-10 03:43, Aaron Hill wrote:

On 2018-05-10 01:04, Phil Holmes wrote:

Did you consider my suggestion of using a Linux virtual machine?


If you are running 64-bit Windows 10, remember that the Windows
Subsystem for Linux exists:

https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux

This seems like the easiest option to be able to run 64-bit build
LilyPond on Windows, until such time as mingw-w64 can be utilized by
LilyPond/GUB.

Obviously, one can run a full VM, but WSL is a much lighter-weight
option with fairly good support for command-line tools.  I am in the
process of getting this set up myself for some work on other projects,
and I will report back my results.


And it works!  I was able to compile Brent's original 194-page epic with 
no problems apart from a missing glyph:


warning: no glyph for character U+201F in font 
`/usr/local/lilypond/usr/share/lilypond/current/fonts/otf/texgyreschola-regular.otf'


This was done by following the installation guide here:

https://docs.microsoft.com/en-us/windows/wsl/install-win10

I opted for the Ubuntu distribution, but there are options for Debian, 
openSUSE, and Kali as well.


After installation, I did `apt-get update` and `apt-get dist-upgrade` 
which put me on 16.04.4 LTS.  Then I installed the latest 64-bit 
LilyPond for Linux:


http://lilypond.org/downloads/binaries/linux-64/lilypond-2.19.81-1.linux-64.sh

I also tested the stress snippet I posted to bug-lilypond that had 
failed on the mingw-w32 build:


%%% stress.ly
\version "2.19.80"
\repeat unfold 36 {
  << { e'8 f' } \\ { c'4 } >> d'4
  << { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >>
}
%%%

As expected, this worked just fine under WSL, even after upping the 
repeats to 2048:



$ time lilypond stress.ly
. . .
[1968][1976][1984][1992][2000][2008][2016][2024][2032][2040][2048]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 39 or 40 pages...
Drawing systems...
Layout output to `/tmp/lilypond-QVyk9u'...
Converting to `stress.pdf'...
Deleting `/tmp/lilypond-QVyk9u'...
Success: compilation successfully completed

real2m16.331s
user1m56.906s
sys 0m15.547s


I was able to segfault with the repeats at 8192.  But that might have 
been an out-of-memory issue.  I only have 6GB physical RAM, and I could 
see that Windows had expanded the pagefile to nearly 24GB trying to 
accommodate the ever-growing lilypond process.



[8120][8128][8136][8144][8152][8160][8168][8176][8184][8192]
Preprocessing graphical objects...Segmentation fault (core dumped)


While the average user is unlikely to go through this process, WSL does 
seem to offer a reasonable stopgap until a working mingw-w64 build of 
LilyPond is available.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-10 Thread Aaron Hill 

On 2018-05-10 01:04, Phil Holmes wrote:

Did you consider my suggestion of using a Linux virtual machine?


If you are running 64-bit Windows 10, remember that the Windows 
Subsystem for Linux exists:


https://en.wikipedia.org/wiki/Windows_Subsystem_for_Linux

This seems like the easiest option to be able to run 64-bit build 
LilyPond on Windows, until such time as mingw-w64 can be utilized by 
LilyPond/GUB.


Obviously, one can run a full VM, but WSL is a much lighter-weight 
option with fairly good support for command-line tools.  I am in the 
process of getting this set up myself for some work on other projects, 
and I will report back my results.


-- Aaron Hill

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-10 Thread Phil Holmes 
Did you consider my suggestion of using a Linux virtual machine?

--
Phil Holmes


  - Original Message - 
  From: Brent Annable 
  To: Michael Gerdau 
  Cc: lilypond-user@gnu.org 
  Sent: Thursday, May 10, 2018 4:14 AM
  Subject: Re: Fwd: Compile crashing... help!


  Being a layman, most of this is all going over my head. But I gather that 
compiling this particular project will not be possible for the time being on my 
current machine, so I’ll either try to get my decrepit laptop up and running, 
or ask a friend to help out :-)

  Thanks for the replies,

  Brent.

  On Thu, 10 May 2018 at 6:55 am, Michael Gerdau <m...@qata.de> wrote:

> I have no idea what it would entail to also provide 64bit Windows
> binaries.

Last time I looked (about 1.5 years ago) the problem was a missing
mingw-w64 package that exists for mingw (the 32bit version) for which I
think it is not actually required for the lilypond build, only for GUB
in general.

I'm not very knowledgeable w/r to GUB. So here is a question for those
with better knowledge:
Is it possible to reduce the required packages for GUB for particular
software (as in lilypond)?

If that's the case I'd expect it to be fairly straight forward to
replace the mingw stuff by mingw-w64 since the later is (or was)
supposed to be a dropin replacement for the former.

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user



--


  ___
  lilypond-user mailing list
  lilypond-user@gnu.org
  https://lists.gnu.org/mailman/listinfo/lilypond-user
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Brent Annable 
FWIW, I just tried this out on my decrepit Windows 7 machine (64-bit, 8GB,
i7 core). After about 8 minutes of whizzing and whirring at 12% CPU
capacity and utilising just under 5 GB of RAM, it returned the same error.

Brent.


On Thu, 10 May 2018 at 1:14 pm, Brent Annable 
wrote:

> Being a layman, most of this is all going over my head. But I gather that
> compiling this particular project will not be possible for the time being
> on my current machine, so I’ll either try to get my decrepit laptop up and
> running, or ask a friend to help out :-)
>
> Thanks for the replies,
>
> Brent.
> On Thu, 10 May 2018 at 6:55 am, Michael Gerdau  wrote:
>
>> > I have no idea what it would entail to also provide 64bit Windows
>> > binaries.
>>
>> Last time I looked (about 1.5 years ago) the problem was a missing
>> mingw-w64 package that exists for mingw (the 32bit version) for which I
>> think it is not actually required for the lilypond build, only for GUB
>> in general.
>>
>> I'm not very knowledgeable w/r to GUB. So here is a question for those
>> with better knowledge:
>> Is it possible to reduce the required packages for GUB for particular
>> software (as in lilypond)?
>>
>> If that's the case I'd expect it to be fairly straight forward to
>> replace the mingw stuff by mingw-w64 since the later is (or was)
>> supposed to be a dropin replacement for the former.
>>
>> Kind regards,
>> Michael
>> --
>>  Michael Gerdau   email: m...@qata.de
>>  GPG-keys available on request or at public keyserver
>>
>> ___
>> lilypond-user mailing list
>> lilypond-user@gnu.org
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
>>
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Brent Annable 
Being a layman, most of this is all going over my head. But I gather that
compiling this particular project will not be possible for the time being
on my current machine, so I’ll either try to get my decrepit laptop up and
running, or ask a friend to help out :-)

Thanks for the replies,

Brent.
On Thu, 10 May 2018 at 6:55 am, Michael Gerdau  wrote:

> > I have no idea what it would entail to also provide 64bit Windows
> > binaries.
>
> Last time I looked (about 1.5 years ago) the problem was a missing
> mingw-w64 package that exists for mingw (the 32bit version) for which I
> think it is not actually required for the lilypond build, only for GUB
> in general.
>
> I'm not very knowledgeable w/r to GUB. So here is a question for those
> with better knowledge:
> Is it possible to reduce the required packages for GUB for particular
> software (as in lilypond)?
>
> If that's the case I'd expect it to be fairly straight forward to
> replace the mingw stuff by mingw-w64 since the later is (or was)
> supposed to be a dropin replacement for the former.
>
> Kind regards,
> Michael
> --
>  Michael Gerdau   email: m...@qata.de
>  GPG-keys available on request or at public keyserver
>
> ___
> lilypond-user mailing list
> lilypond-user@gnu.org
> https://lists.gnu.org/mailman/listinfo/lilypond-user
>
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Michael Gerdau 
> I have no idea what it would entail to also provide 64bit Windows
> binaries.

Last time I looked (about 1.5 years ago) the problem was a missing
mingw-w64 package that exists for mingw (the 32bit version) for which I
think it is not actually required for the lilypond build, only for GUB
in general.

I'm not very knowledgeable w/r to GUB. So here is a question for those
with better knowledge:
Is it possible to reduce the required packages for GUB for particular
software (as in lilypond)?

If that's the case I'd expect it to be fairly straight forward to
replace the mingw stuff by mingw-w64 since the later is (or was)
supposed to be a dropin replacement for the former.

Kind regards,
Michael
-- 
 Michael Gerdau   email: m...@qata.de
 GPG-keys available on request or at public keyserver



signature.asc
Description: OpenPGP digital signature
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread David Kastrup 
Samuel Speer  writes:

> On Wed, May 9, 2018 at 10:44 AM David Kastrup  wrote:
>
>> 1.82G is a bit of a strange number for a 64bit binary.  Are you using a
>> 64bit Windows and definitely a 64bit LilyPond (!) executable?
>>
>
> I checked my executable and it looks to be 32-bit. However, I couldn't find
> a 64-bit version on lilypond.org or at
> http://lilypond.org/downloads/binaries/
>
> Perhaps 64-bit releases for Windows aren't currently being built? Or more
> likely, I just don't know where to find them.

Oh.  The way it looks, we indeed only provide 32bit executables for
Windows (at least there is only one Mingw installer).  So it would
appear that you are indeed running out of memory.  Now make no mistake:
2GB for a 100-page document are pretty silly but LilyPond's grob storage
requirements are indeed excessive currently.  No work toning them down
has been done so far, so you'll not likely fare better with current
master.

I have no idea what it would entail to also provide 64bit Windows
binaries.

Would it be an option to try running a 64bit Linux executable under a
VM?  I'll readily agree that this an utter nuisance and not a viable
state at the current point of time but I cannot think of a better quick
fix right now.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Samuel Speer 
On Wed, May 9, 2018 at 10:44 AM David Kastrup  wrote:

> 1.82G is a bit of a strange number for a 64bit binary.  Are you using a
> 64bit Windows and definitely a 64bit LilyPond (!) executable?
>

I checked my executable and it looks to be 32-bit. However, I couldn't find
a 64-bit version on lilypond.org or at
http://lilypond.org/downloads/binaries/

Perhaps 64-bit releases for Windows aren't currently being built? Or more
likely, I just don't know where to find them.

Sam
___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Timothy Lanfear 

On 09/05/18 15:42, Karlin High wrote:

On 5/9/2018 8:16 AM, Ben wrote:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.


Curiouser and curiouser... It compiled successfully on my Windows 7 
Pro x64 SP1, Intel Core i5-3450, 24 GB RAM, LilyPond 2.19.80


I also successfully compiled this score with Windows 7 Enterprise, Intel 
Core i7-4600, 8 GB RAM, LilyPond 2.19.81.


This example, reported on the bugs list as crashing on Windows, also 
built successfully.


\version "2.19.80"
\repeat unfold 36 {
  << { e'8 f' } \\ { c'4 } >> d'4
  << { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >>
}



--
Timothy Lanfear, Bristol, UK.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread David Kastrup 
tyronicus  writes:

> Phil Holmes wrote
>> My guess is that there's a memory allocation problem that only shows up on
>> large projects on Windows.
>
> That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw
> it cut out around 1.85G memory every time. When I remove two bookparts, it
> only uses 1.82G of memory or so and manages to complete. When I set the
> process to high or realtime priority, which should allow more memory to be
> allocated, it still fails.

1.82G is a bit of a strange number for a 64bit binary.  Are you using a
64bit Windows and definitely a 64bit LilyPond (!) executable?

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread tyronicus 
Phil Holmes wrote
> My guess is that there's a memory allocation problem that only shows up on
> large projects on Windows.

That's my suspicion, too. I tried it on a Win10 i7-8xxx with 8G ram and saw
it cut out around 1.85G memory every time. When I remove two bookparts, it
only uses 1.82G of memory or so and manages to complete. When I set the
process to high or realtime priority, which should allow more memory to be
allocated, it still fails.



--
Sent from: http://lilypond.1069038.n5.nabble.com/User-f3.html

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Phil Holmes 
Might be simplest to create a Linux VM on the Windows box and use that for very 
big projects.  My guess is that there's a memory allocation problem that only 
shows up on large projects on Windows.

--
Phil Holmes


  - Original Message - 
  From: Brent Annable 
  To: David Kastrup 
  Cc: lilypond-user 
  Sent: Wednesday, May 09, 2018 2:59 PM
  Subject: Re: Fwd: Compile crashing... help!


  Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad 
machine with i7 and 16GB RAM. So looks like the errors are coming through on 
the same systems.


  Sigh. What to do? I have an old laptop with a rocket-engine fan that I could 
try


  Brent.


  On 9 May 2018 at 23:28, David Kastrup <d...@gnu.org> wrote:

Ben <soundsfromso...@gmail.com> writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.

With an i5 2520M:

dak@lola:/tmp$ time lilypond SG_complete_DE.ly 
GNU LilyPond 2.21.0
Processing `SG_complete_DE.ly'
Parsing...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][192]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 10 or 11 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 11 or 12 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Karlin High 

On 5/9/2018 8:16 AM, Ben wrote:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.


Curiouser and curiouser... It compiled successfully on my Windows 7 Pro 
x64 SP1, Intel Core i5-3450, 24 GB RAM, LilyPond 2.19.80

--
Karlin High
Missouri, USA

PS - Never saw this piece of music before, looks very interesting.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Re: Fwd: Compile crashing... help!

2018-05-09 Thread Mats Bengtsson 



On 2018-05-09 15:59, Brent Annable wrote:
Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 
Thinkpad machine with i7 and 16GB RAM. So looks like the errors are 
coming through on the same systems.


Sigh. What to do? I have an old laptop with a rocket-engine fan that I 
could try


A first step could be to add
\pointAndClickOff
at the top of your file. At least, it will reduce the size of the 
resulting PDF file by almost a factor of 10, and hopefully it might 
reduce some of the memory consumption during the processing as well.


Can 
http://blogs.microsoft.co.il/sasha/2016/01/05/windows-process-memory-usage-demystified/ 
provide some hints on how to debug what is the limiting factor?


   /Mats



Brent.

On 9 May 2018 at 23:28, David Kastrup > wrote:


Ben >
writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching
capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes
total.




___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread David Kastrup 
Brent Annable  writes:

> Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad
> machine with i7 and 16GB RAM. So looks like the errors are coming through
> on the same systems.
>
> Sigh. What to do? I have an old laptop with a rocket-engine fan that I
> could try

I consider it more likely that it's the version of gcc this has been
compiled with.  That would point to either using different LilyPond
versions or a different architecture as a short-term evasion attempt.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Ben 

On 5/9/2018 9:59 AM, Brent Annable wrote:
Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 
Thinkpad machine with i7 and 16GB RAM. So looks like the errors are 
coming through on the same systems.


Sigh. What to do? I have an old laptop with a rocket-engine fan that I 
could try


Brent.


Hard to decide what to do with our Windows compilations here.  We
don't
want to release when stuff keeps crashing for Windows users.

-- 
David Kastrup


___
lilypond-user mailing list
lilypond-user@gnu.org 
https://lists.gnu.org/mailman/listinfo/lilypond-user





Brent, if you are able to use that laptop for a Linux machine you could 
have two weapons in your arsenal for LilyPond projects... Windows and 
Linux. :)


But the rocket-engine fan sounds pretty promising too... ;)


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Brent Annable 
Thanks everyone. Yeah I forgot to mention: I'm on a Windows 10 Thinkpad
machine with i7 and 16GB RAM. So looks like the errors are coming through
on the same systems.

Sigh. What to do? I have an old laptop with a rocket-engine fan that I
could try

Brent.

On 9 May 2018 at 23:28, David Kastrup  wrote:

> Ben  writes:
>
> > On 5/9/2018 8:35 AM, Brent Annable wrote:
> >> Hi everyone,
> >>
> >> I'm trying to compile a very large project, it keeps crashing and
> >> I'm at a loss as to the cause. Some details:
> >>
> >> - The error first appears as a Windows notification saying: "
> >> Runtime error! This application has requested the Runtime to
> >> terminate it in an unusual way. Please contact the application's
> >> support team for more information." The error code in Frescobaldi
> >> varies, I've had 255, 3 and 1073741395.
> >>
> >> - I've monitored my laptop's CPU and memory usage during the
> >> compiling process, and neither even comes close to reaching capacity
> >> (CPU around 30%; Memory 5.6/16 gig).
> >>   the file to compile is 'SG_complete_DE.ly".
> >>
> >> I would be very grateful for any ideas, suggestions or help.
> >>
> >>
> >
> > Hi Brent,
> >
> > I also ran into your issue by compiling "SG_complete_DE.ly" on my
> > Windows 10 machine. 32GB RAM. Newest i7 build.
> > So, there is some consistency...I see the same errors you do.
> >
> > However, I compiled your project successfully (and quite fast) on my
> > Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.
>
> With an i5 2520M:
>
> dak@lola:/tmp$ time lilypond SG_complete_DE.ly
> GNU LilyPond 2.21.0
> Processing `SG_complete_DE.ly'
> Parsing...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168][176][184][192][192]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144]
> Preprocessing graphical objects...
> Interpreting music...[8][16][24][32][40][48][56][64][72][80][88][96][
> 104][112][120][128][136][144][152][160][168][176][184][192][
> 200][208][216][224][232][240][248][256]
> Preprocessing graphical objects...
> Finding the ideal number of pages...
> Fitting music on 10 or 11 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 11 or 12 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 13 or 14 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 17 or 18 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 15 or 16 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 15 or 16 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 17 or 18 pages...
> Drawing systems...
> Finding the ideal number of pages...
> Fitting music on 14 or 15 pages...
> Drawing systems...
> Layout output to `/tmp/lilypond-hUOD1g'...
> Converting to `SG_complete_DE.pdf'...
> Deleting

Re: Fwd: Compile crashing... help!

2018-05-09 Thread David Kastrup 
Ben  writes:

> On 5/9/2018 8:35 AM, Brent Annable wrote:
>> Hi everyone,
>>
>> I'm trying to compile a very large project, it keeps crashing and
>> I'm at a loss as to the cause. Some details:
>>
>> - The error first appears as a Windows notification saying: "
>> Runtime error! This application has requested the Runtime to
>> terminate it in an unusual way. Please contact the application's
>> support team for more information." The error code in Frescobaldi
>> varies, I've had 255, 3 and 1073741395.
>>
>> - I've monitored my laptop's CPU and memory usage during the
>> compiling process, and neither even comes close to reaching capacity
>> (CPU around 30%; Memory 5.6/16 gig).
>>   the file to compile is 'SG_complete_DE.ly".
>>
>> I would be very grateful for any ideas, suggestions or help.
>>
>>
>
> Hi Brent,
>
> I also ran into your issue by compiling "SG_complete_DE.ly" on my
> Windows 10 machine. 32GB RAM. Newest i7 build.
> So, there is some consistency...I see the same errors you do.
>
> However, I compiled your project successfully (and quite fast) on my
> Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.

With an i5 2520M:

dak@lola:/tmp$ time lilypond SG_complete_DE.ly 
GNU LilyPond 2.21.0
Processing `SG_complete_DE.ly'
Parsing...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][192]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144]
Preprocessing graphical objects...
Interpreting 
music...[8][16][24][32][40][48][56][64][72][80][88][96][104][112][120][128][136][144][152][160][168][176][184][192][200][208][216][224][232][240][248][256]
Preprocessing graphical objects...
Finding the ideal number of pages...
Fitting music on 10 or 11 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 11 or 12 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 13 or 14 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 17 or 18 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 15 or 16 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 15 or 16 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 17 or 18 pages...
Drawing systems...
Finding the ideal number of pages...
Fitting music on 14 or 15 pages...
Drawing systems...
Layout output to `/tmp/lilypond-hUOD1g'...
Converting to `SG_complete_DE.pdf'...
Deleting `/tmp/lilypond-hUOD1g'...
Success: compilation successfully completed

real2m29.251s
user2m26.092s
sys 0m2.629s
dak@lola:/tmp$ 

Hard to decide what to do with our Windows compilations here.  We don't
want to release when stuff keeps crashing for Windows users.

-- 
David Kastrup

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Malte Meyn 



Am 09.05.2018 um 15:16 schrieb Ben:
I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.

So, there is some consistency...I see the same errors you do.

However, I compiled your project successfully (and quite fast) on my 
Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.


Old thinkpad with Linux (Manjaro) here too, 4GB RAM, no success because 
of too little memory.


___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user

Re: Fwd: Compile crashing... help!

2018-05-09 Thread Ben 

On 5/9/2018 8:35 AM, Brent Annable wrote:

Hi everyone,

I'm trying to compile a very large project, it keeps crashing and I'm 
at a loss as to the cause. Some details:


- The error first appears as a Windows notification saying: " Runtime 
error! This application has requested the Runtime to terminate it in 
an unusual way. Please contact the application's support team for more 
information." The error code in Frescobaldi varies, I've had 255, 3 
and 1073741395.


- I've monitored my laptop's CPU and memory usage during the compiling 
process, and neither even comes close to reaching capacity (CPU around 
30%; Memory 5.6/16 gig).

  the file to compile is 'SG_complete_DE.ly".

I would be very grateful for any ideas, suggestions or help.




Hi Brent,

I also ran into your issue by compiling "SG_complete_DE.ly" on my 
Windows 10 machine. 32GB RAM. Newest i7 build.

So, there is some consistency...I see the same errors you do.

However, I compiled your project successfully (and quite fast) on my 
Linux Mint laptop, 2GB RAM, old thinkpad. Took about 3 minutes total.


Hope this helps you.

___
lilypond-user mailing list
lilypond-user@gnu.org
https://lists.gnu.org/mailman/listinfo/lilypond-user