Janek Warchoł <janek.lilypond <at> gmail.com> writes: > i've decided that instead of complaining about slowed development > process, i can do some bug-fixing instead. >
You could experiment to understand better the situations that lead to the out-of-memory crash under Windows --- issue 3432 and other reports on bug- lilypond yesterday. This makes version 2.17.21 useless on Windows. It is difficult to debug in the traditional ways, because it does not happen in the development environments: Linux or BSD-style MacOS. Looking at the commits since version 2.17.20, the only one that seems related is my change to outside-staff-padding, but I cannot imagine a way for that change to cause this problem. The problem seems to need text that uses skylines being placed outside the staff. Tiny changes to the text avoid the problem, including adding spaces to the start of the text. I have not investigated whether the problem affects lyrics (which are place in their own verticalAxisGroup) or dynamics (which can be placed against the staff or in a Dynamics). You would want to find a way to recognize the problem before Windows starts to page memory to disk, because that slows the system down quite a lot. _______________________________________________ lilypond-devel mailing list lilypond-devel@gnu.org https://lists.gnu.org/mailman/listinfo/lilypond-devel
