Changing color of tie and slur at the same time crashes the program
Reported version
3.6
Type
Functional
Frequency
Once
Severity
S2 - Critical
Reproducibility
Always
Status
fixed
Regression
No
Workaround
Yes
Project
Dear MuseScore team,
It's a minor layout or functional bug but every time I do this, it crashes the program.
Steps to reproduce the issue:
1) Select at least one slur and one tie together to have them selected as a group
2) Go to 'Inspector' and click with the mouse on the element 'Color'
3) Program crashes
This was the case every time I tried it or just didn't keep it in mind.
Workaround: When I select only some ties OR some slurs in a group for changing color it won't happen.
I couldn't find this issue in the tracker.
I hope my description is understandable since English is not my mother tongue.
Thank you for all efforts. I love working with the MuseScore program.
Best wishes to you!
Attachment | Size |
---|---|
ties and slurs.JPG | 28.35 KB |
Fix version
4.0.0
Comments
I can confirm this.
a (pretty useless?) stack trace:
1 ntdll!RtlIsZeroMemory 0x7fff9694f123
2 ntdll!RtlpNtSetValueKey 0x7fff96957ee2
3 ntdll!RtlpNtSetValueKey 0x7fff969581ca
4 ntdll!RtlpNtSetValueKey 0x7fff9695de51
5 ntdll!RtlGetCurrentServiceSessionId 0x7fff96875bf0
6 ntdll!RtlFreeHeap 0x7fff968747b1
7 msvcrt!free 0x7fff96289c9c
8 QObjectPrivate::deleteChildren() 0x68a912ee
9 QWidget::~QWidget() 0x327ef1e2
10 Awl::ColorLabel::~ColorLabel colorlabel.cpp 35 0x8e9bc4
11 Awl::ColorLabel::~ColorLabel colorlabel.cpp 38 0x8e9be7
12 QObjectPrivate::deleteChildren() 0x68a912ee
13 QWidget::~QWidget() 0x327ef1e2
14 QWidget::~QWidget() 0x327ef3ed
15 QObjectPrivate::deleteChildren() 0x68a912ee
16 QWidget::~QWidget() 0x327ef1e2
17 QWidget::~QWidget() 0x327ef3ed
18 QObjectPrivate::deleteChildren() 0x68a912ee
19 QWidget::~QWidget() 0x327ef1e2
20 Ms::InspectorBase::~InspectorBase inspectorBase.h 50 0xefb6e4
...
OS: Windows 11 Version 2009 or later, Arch.: x86_64, MuseScore Studio version (64-bit): 4.4.4-243461245, revision: 2232670
I often change the colour of slurs and ties to a dark gray if they are crossing through a lot of other voice notes in a measure.
At some point in 4.x it started crashing the program. Unlike the case reported for 3.6 I only have to change a single slur or tie. The program always crashes.
This issue tracker has been discontinued (some 2 years ago)
So report on GitHub instead
Fix the program so that it links to Github instead of here. If musescore can't be assed to fix that, I can't be assed to repost.
Where does the program link to this issue tracker here?
As far as I can tell 4.x does no longer have the "Report a Bug" button (which in older version indeed led here, but even that doesn't work any longer).
The 'Ask for help" leads to the forums, not the issue tracker
The new issue tracker is at https://github.com/musescore/MuseScore/issues/new/choose
You want that bug fixed, you report it on the proper place, simple as that. Here it won't get read by the developers (anymore)
Also this issue here is different anyhow: it is abpout a crash when you try to change color (or any other property) of slurs and ties in one go.
That issue still exists in 3.x (and won't get fixed there, it is fixed though in my MuseScore 3.7 Evolution), but not in 4.x anymore
> I often change the colour of slurs and ties to a dark gray if they are crossing through a lot of other voice notes in a measure.
Is the color dark grey significant? I can't reproduce it.
In reply to Also this issue here is… by Jojo-Schmitz
Thank you for once again not reading what I wrote "Unlike the case reported for 3.6 I only have to change a single slur or tie". Get some sleep.
In reply to > I often change the colour… by mercuree
Possibly it's having saved the colour choice in the Windows color palette dialog and then choosing from it again (???)
That workaround did(dies help on Mu3. and, as said, for Mu4 it is a different issue:
Unlike the case reported for 3.6 I only have to change a single slur or tie
Apart from that: I can't reproduce, changing a tie's or slur's color in 4.4.4 on Windows 11 just works
Even both at the same time (which is why I said that this issue here is fixed in Mu4)