Last modified: 2013-05-12 02:50:11 UTC
The following code is interpreted by lilypond without errors does not generate picture nor midi via Score MediaWiki extension. Error message generated does not contain any useful information. https://pl.wikisource.org/wiki/Dyskusja_strony:PL_Tarnowski-Szkice_helweckie_i_Talia.djvu/101 Externally, lilipond generates correct .ps and midi files.
In case it disappears later, here's the error message: Unable to compile LilyPond input file: Processing `/tmp/MWLP.4cb4b46c923bffd256aa103eb3a58fcf/file.ly' Parsing... Interpreting music... [8] Preprocessing graphical objects... Interpreting music... MIDI output to `file.midi'... Finding the ideal number of pages... Fitting music on 1 page... Drawing systems... Layout output to `file.ps'... Converting to PNG...GS exited with status: 9ERROR: In procedure delete-file: ERROR: No such file or directory exited with status: 1
(In reply to comment #0) > Error message generated does not contain any useful information. That's bug 47571. Might be a dup of bug 47534.
this is an out of memory error since its a rather complex composition, one option might be to increase the memory on the apache nodes.
Sounds like a dupe to me. *** This bug has been marked as a duplicate of bug 47534 ***
(In reply to comment #3) > this is an out of memory error since its a rather complex composition, one > option might be to increase the memory on the apache nodes. Just as a note, on my local install, the example renders fine with $wgMaxShellMemory = 55000; which is about half the memory limit used by wmf.
(In reply to comment #5) > (In reply to comment #3) > > this is an out of memory error since its a rather complex composition, one > > option might be to increase the memory on the apache nodes. > > Just as a note, on my local install, the example renders fine with > $wgMaxShellMemory = 55000; which is about half the memory limit used by wmf. Hmm, I close as a dupe, and then keep commenting on it, that's pretty bad practise. Anyhow, just wanted to say I think you're right about it being a resource limit issue, not sure what the deal is with my local test not using that much resources...
