Select Publish Tab & Musescore 4 Crashes

EarthToTom commented 1 year ago

Issue type

Crash or freeze

Bug description

No response

Steps to reproduce

Steps: Double-click any .mscz file to open a score Musescore opens with the Score tab selected Select the Publish tab Musecore crashes

Workaround: Double-click any .mscz file to open a score Select the Home tab Select the Publish tab Musescore will Export a .pdf file

Musescore 4.1.0 Version Info: OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.0-231921402, revision: github-musescore-musescore-2e3a93a

Screenshots/Screen recordings

I don't have video capability

MuseScore Version

Musescore 4.1.0 Version Info: OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.0-231921402, revision: github-musescore-musescore-2e3a93a

Regression

No.

Operating system

OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045

Additional context

2023-07-13T13:24:30.148 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.149 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.150 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.150 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.150 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.151 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.151 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.152 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.152 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.153 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.153 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.154 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.154 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.155 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.155 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:30.156 | ERROR | main_thread | | operator : error: qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth"

2023-07-13T13:24:30.156 | WARN | main_thread | Qt | qrc:/qml/MuseScore/UiComponents/FlatButton.qml:174:5: QML Loader: Binding loop detected for property "itemImplicitWidth" 2023-07-13T13:24:31.270 | WARN | main_thread | AbstractMenuModel | makeMenuItem: not found action: notenames 2023-07-13T13:24:31.692 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(405, 36) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.692 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(405, 36) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.693 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(405, 36) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.693 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(405, 36) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.709 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.709 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.709 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.709 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.710 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.710 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.710 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.710 | WARN | main_thread | Qt | void cdecl Layouting::ItemBoxContainer::setSize_recursive(class QSize,enum Layouting::ChildrenResizeStrategy) New size doesn't respect size constraints ; new= QSize(405, 34) ; min= QSize(473, 46) Layouting::ItemBoxContainer(0x13691770) 2023-07-13T13:24:31.761 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: file-open 2023-07-13T13:24:33.141 | ERROR | 13656 | | operator : INFO chunk size mismatch 2023-07-13T13:24:33.244 | INFO | 13656 | FluidSynth | addSoundFonts: success load soundfont: C:/Program Files/MuseScore 4/sound/MS Basic.sf3 2023-07-13T13:24:33.305 | ERROR | main_thread | | operator : Unable to check for update, error: [1701] 2023-07-13T13:24:33.352 | INFO | 13656 | FluidSynth | addSoundFonts: success load soundfont: C:/Program Files/MuseScore 4/sound/MS Basic.sf3 2023-07-13T13:26:17.285 | WARN | main_thread | Qt | QQmlComponent: Created graphical object was not placed in the graphics scene. 2023-07-13T13:26:23.203 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: about-qt 2023-07-13T13:26:33.594 | WARN | main_thread | Qt | QQmlComponent: Created graphical object was not placed in the graphics scene. 2023-07-13T13:26:36.771 | INFO | main_thread | ActionsDispatcher | dispatch: try call action: about-musescore

System Info: OS Name Microsoft Windows 10 Pro Version 10.0.19045 Build 19045 Other OS Description Not Available OS Manufacturer Microsoft Corporation System Name OMEN System Manufacturer HP System Model OMEN by HP Laptop System Type x64-based PC System SKU W2N48UA#ABA Processor Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz, 2592 Mhz, 4 Core(s), 8 Logical Processor(s) BIOS Version/Date Insyde F.09, 7/19/2016 SMBIOS Version 2.8 Embedded Controller Version 82.27 BIOS Mode UEFI BaseBoard Manufacturer HP BaseBoard Product 825B BaseBoard Version 82.27 Platform Role Mobile Secure Boot State Off PCR7 Configuration Elevation Required to View Windows Directory C:\WINDOWS System Directory C:\WINDOWS\system32 Boot Device \Device\HarddiskVolume3 Locale United States Hardware Abstraction Layer Version = "10.0.19041.2728" User Name OMEN\Earth Time Zone Pacific Daylight Time Installed Physical Memory (RAM) 12.0 GB Total Physical Memory 11.9 GB Available Physical Memory 4.88 GB Total Virtual Memory 13.7 GB Available Virtual Memory 4.78 GB Page File Space 1.81 GB Page File C:\pagefile.sys Kernel DMA Protection Off Virtualization-based security Running Virtualization-based security Required Security Properties
Virtualization-based security Available Security Properties Base Virtualization Support, DMA Protection Virtualization-based security Services Configured
Virtualization-based security Services Running
Device Encryption Support Elevation Required to View A hypervisor has been detected. Features required for Hyper-V will not be displayed.

zacjansheski commented 1 year ago

I don't see this on Windows 11 Have you experienced this with multiple scores?

https://github.com/musescore/MuseScore/assets/69917893/42f60e7f-14ee-43ce-9f66-87a0c61efe53

EarthToTom commented 1 year ago

Yes Zac,

This crash happens to me quite often. I can't say every time since I don't keep track of what I'm doing that closely. I only write songs so the files are pretty small. Sorry, the cpu (processor) on my laptop does not support Windows 11. Eventually, I'll have to update my computer, but ... I was hoping to be able to dedicate my then old one for music purposes. As I mentioned, there is a workaround, but it does seem clumsy. Thanks for responding so promptly.

Best regards,

Tom Russo

@.***

On Thu, Jul 13, 2023 at 2:32 PM Zac Jansheski @.***> wrote:

I don't see this on Windows 11 Have you experienced this with multiple scores?

https://github.com/musescore/MuseScore/assets/69917893/42f60e7f-14ee-43ce-9f66-87a0c61efe53

— Reply to this email directly, view it on GitHub https://github.com/musescore/MuseScore/issues/18582#issuecomment-1634948856, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBILHBFBKJVMFZLN7RJZOALXQBSNZANCNFSM6AAAAAA2JPOGJQ . You are receiving this because you authored the thread.Message ID: @.***>

zacjansheski commented 1 year ago

We have many users on Windows 10 so I hope that it is fixable!

Any additional info to help us diagnose would be greatly appreciated. Are there any patterns with the scores that have these issues or is it all of them for you?

Eism commented 1 year ago

@EarthToTom The attached log doesn't show that you had a crash Please send the diagnostic file: Diagnostic -> Save diagnostic file

EarthToTom commented 1 year ago

~!@# Seems I can't email the diagnostic file. It's too big. Try this downloadable link from Google Drive.

https://drive.google.com/file/d/16LVAwbFNpJ7nRSN9wJaXg5YY9HnXgpIN/view?usp=sharing

Best regards,

Tom Russo

619-800-TOMR (8667)

@.***

On Fri, Jul 14, 2023 at 5:05 PM Tom Russo @.***> wrote:

Hi Elnur,

Sorry about that! This crash occurs pretty much across all my files. It crashed again today when I went to create the diagnostic file I've attached. Steps: Opened a score/song file Selected Publish Musescore 4.1.0 crashed Opened Musescore again Selected Diagnostic > Save diagnostic file Attached the zip file

Hope that shows the crash information you need.

I won't be able to test the build you've attached right now, but I'll try later and get back to you with my experience. BTW: I just updated the program to the latest version, so I have to presume it would have the fix in the build you've suggested, or is it a BETA build?

Best regards,

Tom Russo

619-800-TOMR (8667)

@.***

On Thu, Jul 13, 2023 at 10:37 PM Elnur Ismailzada < @.***> wrote:

@EarthToTom https://github.com/EarthToTom The attached log doesn't show that you had a crash Please send the diagnostic file: Diagnostic -> Save diagnostic file

But it seems to me that this one is very similar to #18558 https://github.com/musescore/MuseScore/issues/18558 So can you test this build? https://github.com/musescore/MuseScore/suites/14274905159/artifacts/802297205

— Reply to this email directly, view it on GitHub https://github.com/musescore/MuseScore/issues/18582#issuecomment-1635301493, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBILHBEBFPDUJTHHXJ4UC5LXQDLH3ANCNFSM6AAAAAA2JPOGJQ . You are receiving this because you were mentioned.Message ID: @.***>

Eism commented 1 year ago

@EarthToTom Could you please check this build https://github.com/musescore/MuseScore/actions/runs/5624778485?

EarthToTom commented 1 year ago

Hi Elnor,

How do I do that? I get to this screen (picture attached)

[image: MusescoreTestBuildRepository.png]

and there's nothing to download. I'd need a downloadable installer to check it out. So sorry if I can't be of much help. I will try if you'll walk me through how to do it,

Best regards,

Tom Russo

619-800-TOMR (8667)

@.***

On Mon, Jul 24, 2023 at 12:18 AM Elnur Ismailzada @.***> wrote:

@EarthToTom https://github.com/EarthToTom Could you please check this build https://github.com/musescore/MuseScore/actions/runs/5624778485?

— Reply to this email directly, view it on GitHub https://github.com/musescore/MuseScore/issues/18582#issuecomment-1647348559, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBILHBHO2NN3TXIYQYD6N33XRYOUXANCNFSM6AAAAAA2JPOGJQ . You are receiving this because you were mentioned.Message ID: @.***>

zacjansheski commented 1 year ago

@EarthToTom we can't see the attached image

Info on running test builds is on Windows is at the bottom of this page (you will need 7-zip) https://github.com/musescore/MuseScore/wiki/Downloading-and-running-test-builds

EarthToTom commented 11 months ago

Success Zac!!!,

I had a chance to test the GitHub posted Musescore 4 build: 4.1.1.232021703 per your request.

The build works beautifully for me.

I can now open the “Publish” tab directly and print out a file - no crashing.

I’m also able to switch back and forth between the “Publish” and “Score” tabs without crashing.

Thanks very much for your help.

Regards, Tom

EarthToTom commented 11 months ago

Hi Elnur,

I’m sorry to report that the test build 4.1.1.232021703 is still crashing during regular use.

My testing was brief and did seem to work at first, but now the program is crashing again.

It happens regularly, as before, when I open a score and attempt to go directly to the “Publish” tab.

Seems this issue may have been closed prematurely.

Actually, I’d much prefer it if you worked on supporting export of the Yamaha XF format for MIDI; I've attached their spec document (xfspec.pdf).

That way I’d be able to drive the auto-accompaniment style files on my Clavinova from the chord symbols I enter on my score.

After all, I do still have the workaround for the “Publish” tab (it works if I go to the “Home” tab first).

Thanks for your troubles just the same.

Best regards,

Tom Russo

619-800-TOMR (8667)

@.***

On Tue, Sep 5, 2023 at 12:09 AM Elnur Ismailzada @.***> wrote:

Closed #18582 https://github.com/musescore/MuseScore/issues/18582 as completed.

— Reply to this email directly, view it on GitHub https://github.com/musescore/MuseScore/issues/18582#event-10279733489, or unsubscribe https://github.com/notifications/unsubscribe-auth/BBILHBDDENU42FKGMDTZEXLXY3F3DANCNFSM6AAAAAA2JPOGJQ . You are receiving this because you were mentioned.Message ID: @.***>

Eism commented 11 months ago

@EarthToTom Hi! Thank you for update. Please attach a new diagnostic file: Diagnostic -> Save diagnostic file

EarthToTom commented 11 months ago

Okay, here's 2 of them. Actually, both were saved after the program crashed and I restored the previous session. I hope that's the appropriate way to capture the system state you need to see. Regards, Tom 2023-09-11-StillCrashes.zip 2023-09-11-AfterRestorePreviousSessionThatCrashed.zip

TomRussoMusic commented 9 months ago

Never mind adding support for the Yamaha XF format. Doing so only seems to transfer chord information to the Lyric display screen on my Clavinova CVP-809. It’s useless for driving styles. It seems to go unrecognized by the SongCreator chord track which is used to drive the Yamaha style auto accompaniment feature. Evidently, the only way to trigger the Yamaha style auto-accompaniment feature is either by playing the keyboard or manual entry of the chord information into the SongCreator chord track. Ergo, the issue is with the Yamaha hardware and not any external XF/XG data transfer. Just thought I’d mention.

kenalesand commented 8 months ago

This exact problem is now happening to me. Windows 11, Musescore 4.2. Publish was working until last night on a new piece. Now happens on all projects (old and new) since. Same work-around applies.

If logs will help I can supply.

iainhallam commented 7 months ago

Still an issue on OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.0-233521124, revision: github-musescore-musescore-eb8d33c.

Open the application
In Home, click new score, then Done (changing nothing)
The blank-ish score opens; click Publish tab
Crash

After restarting, here's my diagnostic files:

2024-01-08 MuseScore 4.2 crash.zip

Clicking on the Home tab first then Publish still works to avert the crash, and you have to also go to the Home tab first when returning from Publish to the Score, otherwise it still crashes.

iainhallam commented 7 months ago

Just for info, still present on OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.2.1-240230937, revision: github-musescore-musescore-d757433.

musescore / MuseScore