In order for us to investigate, we would need you to attach the core that demonstrates this problem, and give us precise steps to reproduce the crash - tell exactly which notes to select and in what order.
If it happens every time, it should be very easy to find a score that demonstrates the problem and to post the precise steps. But since no one else has reported any such problem and none of us is experiencing it, we need your help to reproduce it.
I uninstalled Musescore, went to this site and downloaded and installed the latest version. On the startup dialog, I chose to Open A Score. I tapped the CMD key (the one to the right of the spacebar, not that it should make any difference) and MS crashed. I reopened MS, chose to restore session. The previous score opened. This time I was able to tap the CMD key once. A second press crashed MS. I tried this twice. Then I decided to restart MS without restoring. I chose to Create New Score. I chose Treble Clef->Done. I placed a quarter note at F above middle C, then clicked out of note entry mode. This time MS crashed on a third tap of CMD - at no time was my mouse cursor over a note.
Oh, actually, one thing I do recall - seems there was a report of bug in a certain version of macOS and or Qt where if you've turned on some special option having to do with popup windows, it can cause applications to crash. See https://musescore.org/en/node/317321#comment-1061914.
This issue may now be closed. This resolved the problem. If it helps anyone else, MacOS 11.5.2 still has this problem, it appears, or it may be a problem with QT.
Comments
In order for us to investigate, we would need you to attach the core that demonstrates this problem, and give us precise steps to reproduce the crash - tell exactly which notes to select and in what order.
In reply to In order for us to… by Marc Sabatella
I can hold CMD, and click ANY note ANYWHERE in ANY score and MS crashes instantly. Every, Single. Time.
So you're saying that https://musescore.org/en/handbook/3/selection-modes#list-select isn't working for you?
As you apparently are the only one having this issue, try https://musescore.org/en/handbook/3/revert-factory-settings
In reply to Try https://musescore.org/en… by Jojo-Schmitz
If it happens every time, it should be very easy to find a score that demonstrates the problem and to post the precise steps. But since no one else has reported any such problem and none of us is experiencing it, we need your help to reproduce it.
I uninstalled Musescore, went to this site and downloaded and installed the latest version. On the startup dialog, I chose to Open A Score. I tapped the CMD key (the one to the right of the spacebar, not that it should make any difference) and MS crashed. I reopened MS, chose to restore session. The previous score opened. This time I was able to tap the CMD key once. A second press crashed MS. I tried this twice. Then I decided to restart MS without restoring. I chose to Create New Score. I chose Treble Clef->Done. I placed a quarter note at F above middle C, then clicked out of note entry mode. This time MS crashed on a third tap of CMD - at no time was my mouse cursor over a note.
Oh, actually, one thing I do recall - seems there was a report of bug in a certain version of macOS and or Qt where if you've turned on some special option having to do with popup windows, it can cause applications to crash. See https://musescore.org/en/node/317321#comment-1061914.
In reply to Try https://musescore.org/en… by Jojo-Schmitz
"So you're saying that https://musescore.org/en/handbook/3/selection-modes#list-select isn't working for you?"
It's more precise to say that this causes a crash.
"Hold down Ctrl (Mac: Cmd) and successively click on the desired additional elements."
Now, simply holding or even tapping the CMD key causes a crash; see my new report.
In reply to Oh, actually, one thing I do… by Marc Sabatella
This issue may now be closed. This resolved the problem. If it helps anyone else, MacOS 11.5.2 still has this problem, it appears, or it may be a problem with QT.
So a duplicate of #317323: macOS 10.5 accessibility setting “Enable Hover Text” causes crash?
BTW reinstall does keep the settings, so reverting those to factory defaults is still on your Todo list :-)
"So a duplicate of #317323: macOS 10.5 accessibility setting “Enable Hover Text” causes crash?"
Yes. It won't won't be necessary to revert to factory settings as disabling Enable Hover Text solves the problem.
True.