Re: Fatal error compiling large project (Win10/2.19.82)

[Saul Tobin]

It looks like the Fatal realloc error happens after the score finishes compiling while it's being written to a temporary file. At that point, the Lilypond process is using ~1.8 G of RAM. Is it possible I'm running into a 32 bit size limitation in Guile or something like that?

On Sun, Dec 16, 2018 at 4:14 PM Saul Tobin <address@hidden> wrote:

Hi Ben,

I did see that thread, but I don't think it can be directly related to my issue, since in my case there is no single line of my code that is triggering the compile error. Each score compiles correctly on its own and in combination with any of the others, but when I compile all together it fails. I am also not using strftime anywhere.

Saul

On Sun, Dec 16, 2018 at 2:38 PM Ben <address@hidden> wrote:

On 12/16/2018 5:32 PM, Saul Tobin wrote:

Hi all,

I'm getting a fatal error when I compile all of the movements of a large project on 2.19.82 on Windows 10. I can compile the movements individually and in smaller combinations with no problems. There is no Lilypond error in the debug output, just "FATAL: memory error in realloc."

I had no issues with this project on 2.18.2, and the only changes between versions were running convert-ly and changing a couple variable names.

Totally stumped here. Ideas?

Saul

Hi Saul,

I believe it's a Windows only bug/issue/problem/headache, sorry :(

See here for a similar problem:

http://lilypond.1069038.n5.nabble.com/Fatal-bug-in-strftime-td145721.html

There may be a workaround for you, aside from going through the trouble of setting up a virtual machine just to compile ;)

Do you have any concerns with file names or other things that could be triggering the memory error? Any other log info?

_______________________________________________
lilypond-user mailing list
address@hidden
https://lists.gnu.org/mailman/listinfo/lilypond-user