Re: GS error on somewhat large score

[Knut Petersen]

Am 16.10.2017 um 19:23 schrieb Simon Albrecht:
> On 16.10.2017 18:50, David Kastrup wrote:
> > Simon Albrecht <address@hidden> writes:
> > > On 16.10.2017 17:13, David Kastrup wrote:
> > > > Simon Albrecht <address@hidden> 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 

The glib function g_spawn_sync() is called from  our general-scheme.cc file in 
ly_run_command().

It seems your system is low on memory. Did you set a limit on memory usage?

You might run lilypond under control of gdb, set a breakpoint at the start of 
ly_run_command() and inspect memory usage when the breakpoint is reached.

Or temporarily replace "gs" with a script that ignores the arguments and 
executes a tool that allows you  to inspect the amount of free memory.

Try to increase the amount of available memory by adding some more GB of swap.

Knut