Crash on opening 2.0.3 file due to invisible ties
Win 7 / eb36276
This is a 2.0.3 file that causes the nightly to crash when opened. The immediate cause is the presence of invisible ties in the tablature staff. When these ties are all made visible the file will open in the nightly (albeit with other bugs detailed elsewhere).
Attachment | Size |
---|---|
crash_invisible_ties.mscz | 10.85 KB |
Comments
stack trace :
1 Ms::SpannerSegment::setVisible spanner.cpp 168 0x83dfa5
2 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
3 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
4 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
5 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
6 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
7 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
8 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
9 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
10 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
11 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
12 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
13 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
14 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
15 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
16 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
17 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
18 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
19 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
20 Ms::SpannerSegment::setVisible spanner.cpp 175 0x83e07f
...
and therefor a duplicate of #142141: Crash when trying to open file with tied unison notes in different voices
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.