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

[MU4 Issue] MS 3.6 Plugin Crashes in MS4 Nightly #13089

Closed
JeffRocchio opened this issue Aug 30, 2022 · 1 comment
Closed

[MU4 Issue] MS 3.6 Plugin Crashes in MS4 Nightly #13089

JeffRocchio opened this issue Aug 30, 2022 · 1 comment

Comments

@JeffRocchio
Copy link

A custom build plugin I run nearly daily in MS 3.6 crashes MS4 nightly build.

I have included links to the console output, the plugin code, and the score against which I run the plugin as file attachments.

Summary:

Running MS4 nightly build of 2022-08-29

Attempting to run my custom plugin: MtnDulcimer-CromoTABtoDiatonic_rel-1.0.qml. The plugin QML file is in /home/jroc/Documents/MuseScore4Development/Plugins/ and is seen by MS4, and appears in the MS4 Plugins menu. This plugin runs sucessfully (on a nearly daily basis) in MS3.6. I am attempting to run it as-is in MS4 nightly, I've not made any changes from the version I run in MS3.6. The plugin does appear to run to conclusion prior to crashing MS4, as I am able to see, for a brief half-second, the final popup window I present the user with upon successful completion.

I do see a few of these warning statements in the console output:

"16:26:32.200 | WARN | main_thread | QmlPlugin | setMenuPath: Not supported!! Use:title."

So I did try commenting out the menuPath: statement in my plugin's code, but that had no effect.

I am on fedora Linux 35

Attachments:

Issue_3.6-Plugin-Crashes_ConsoleLog.txt

Test-3.6Plugin-Parts.pdf

MtnDulcimer-CromoTABtoDiatonic_rel-1.0.pdf

@JeffRocchio
Copy link
Author

This is caused by the use of Qt.quit() in the plugin code. When I modify the code to change Qt.quit() to quit() then my 3.6 plugins run fine. See issue #13222.

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

No branches or pull requests

1 participant