|
From: | Aaron Hill |
Subject: | Re: Lilypond 2.19.80-1 hangs |
Date: | Sun, 06 May 2018 00:49:15 -0700 |
User-agent: | Roundcube Webmail/1.3.6 |
On 2018-05-05 17:01, Aaron Hill wrote:
How about this repro: %%% \version "2.19.80" \repeat unfold 36 { << { e'8 f' } \\ { c'4 } >> d'4 << { g'4. f'8 } \\ { e'16 d' e'4 d'8 } >> } %%% On my machine, I cannot compile this as-is without the LilyPond process ending prematurely with an access violation:Faulting application name: lilypond.exe, version: 2.19.80.1, time stamp: 0x0000000b Faulting module name: lilypond.exe, version: 2.19.80.1, time stamp: 0x0000000bException code: 0xc0000005 Fault offset: 0x000ea392If I lower the repeats to 35 or if I alter the expressions to remove a note (e.g. change { e'8 f' } to { e'4 }), it works. Here are some system details:Operating System: Windows 10 Pro 64-bit (10.0, Build 16299) (16299.rs3_release.170928-1534)Processor: Intel(R) Core(TM)2 Duo CPU T9500 @ 2.60GHz (2 CPUs) Memory: 6144MB Page File: 3362MB used, 3804MB availableI could install WinDbg and dig in further, if it would help. However, I would need symbols for the Windows build.
So this is a bit of a Heisenbug we have here. When running under a debugger, the access violation does not want to occur. However, after setting up Dr. MinGW (https://github.com/jrfonseca/drmingw) as my post-mortem debugger, I was able to get the following:
lilypond.exe caused an Access Violation at location 00000000004EA392 in module lilypond.exe Reading from location 000000000714E55C.Registers:eax=0714e550 ebx=0a24c130 ecx=0a24c130 edx=0a289448 esi=0a247f78 edi=00000002 eip=004ea392 esp=00b0d7ac ebp=07059948 iopl=0 nv up ei pl nz na po nc cs=0023 ss=002b ds=002b es=002b fs=0053 gs=002b efl=00010206AddrPC Params 004EA392 07154BB0 05975BB0 07142110 lilypond.exe!Grob_info::context004343D4 00000000 00000000 00000000 lilypond.exe!Beam_collision_engraver::finalize
-- Aaron Hill
[Prev in Thread] | Current Thread | [Next in Thread] |