Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef #5481

Merged
merged 1 commit into from Dec 2, 2019

Conversation

Jojo-Schmitz
Copy link
Contributor

@Jojo-Schmitz Jojo-Schmitz commented Nov 19, 2019

which seems to not belong to any segment, so dereferences a NULL pointer leading to a segment violation (pun intended).
The fix simply ignores this, and this avoids the crash, but also looses the 'visible' property of that clef for some yet unknown but unrelated reason.

Solves https://musescore.org/en/node/297310 / https://musescore.org/en/node/297326

…ace setting on the initial clef

which seems to not belong to any segment, so dereferences a NULL pointer
leading to a segment violation (pun intended).
The fix simply ignores this, and this avoids the crash, but also looses
the 'visible' property of that clef for some yet unknown but unrelated reason.
@Jojo-Schmitz Jojo-Schmitz changed the title fix #297310: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef fix #297326: Crash on opening Musescore 2.x file that uses leading space setting on the initial clef Nov 19, 2019
@dmitrio95 dmitrio95 merged commit 3d9c900 into musescore:master Dec 2, 2019
@Jojo-Schmitz Jojo-Schmitz deleted the segment-violation branch December 2, 2019 12:16
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants