Simon Albrecht <simon.albre...@mail.de> writes: > On 16.10.2017 18:50, David Kastrup wrote: >> Simon Albrecht <simon.albre...@mail.de> writes: >>> On 16.10.2017 17:13, David Kastrup wrote: >>>> Simon Albrecht <simon.albre...@mail.de> writes: >>>>> Hello everybody, >>>>> >>>>> I’ve just noticed a problem when compiling a medium to large score (44 >>>>> pages of output) with 2.19.65: everything is fine until GS fails with >>>>> the message >>>>> warning: g_spawn_sync failed (0): gs: Failed to fork (Cannot allocate >>>>> memory). >>>>> Compiling the 3–5 page bookparts individually is no problem. >>>>> >>>>> Does this ring a bell with anybody? or >>>>> How should I further investigate the problem? or >>>>> Would anybody be interested in getting the file privately to investigate? >>>> It might be worth mentioning what kind of system and which Ghostscript >>>> you are seeing this problem with. >>> Ubuntu 16.04. >> This is great. Now we only need to know your system architecture >> (64bit? 32bit? arm? x86?), whether you installed the system version of >> LilyPond or a predistributed binary or compiled something yourself, your >> Ghostscript version. > > $ uname -m > x86_64 > > I already said that I use LilyPond 2.19.65, and meant to imply that > this is the default bundled version. It calls Ghostscript version > 9.21, which is contained in the bundle.
So how much memory do you have and how much swap space? -- David Kastrup _______________________________________________ lilypond-user mailing list lilypond-user@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-user
