Note Input State Interactions with Plugins/Plugin Creator that crash Musescore

• Jun 28, 2021 - 11:17
Type
Plugins
Frequency
Few
Severity
S2 - Critical
Reproducibility
Always
Status
active
Regression
No
Workaround
No
Project

I am using Windows 10 (Musescore 3.6.2 and the latest nightly build) and have found the following bugs in interactions with plugins and the UI Note Input state:

1) Running the "Hello World" plugin that is generated using the "Create New" button at the top of the Plugin Creator from the Plugin Creator will cause Musescore to crash (evaporate) if the user interface is in Note Input state . In fact, running any plugin from the Plugin Creator will cause Musescore to crash (evaporate) if the UI is in a Note Input state. There is normally a few/several seconds delay after executing the plugin before Musescore crashes.

But if you are quick at clicking on the main musescore UI you can prevent the crash.

2) If a plugin that contains the executable line (and the UI is not currently in a Note Input state):

cmd("note-input") //This should put the UI in a Note Input state

it will cause Musescore to crash (evaporate). The crash occurs whether the plugin is run form the Plugin Creator or from the UI. There is normally a few/several seconds delay after executing the plugin before Musescore crashes.

However if you duplicate the note input command, i.e. have code like:

cmd("note-input")
cmd("note-input")

Everything works OK (except you don't get to put the UI in a Note Input state!). Presumably the second instance of the command takes Musescore out of an unstable state before it can crash.

3) If Musescore is put in a Note Input state through the UI, and you open (or have open) the Plugin Creator and have a plugin displayed and you click on the text editor part of the Plugin Creator and then click on the main UI it will cause Musescore to crash.

A comment from jojo-schmitz (Plugin Forum - https://musescore.org/en/node/322558 ) indicates this issue has occurred in some previous versions:

"It is not a new bug though, happens too with 3.3.4 (the Microsoft Store version) and also with 2.3.2"


Comments