musescore / musescore/MuseScore

Unexpected quit/crashing - when opening or saving a file

Open
#18,970 4 comments 0 reactions 1 assignee View on GitHub

@RomanPudashkin is already working on this.

Since Aug 8, 2023.

crash P3 regression MS3
Dominant language
C++
Stars
15.1k
Forks
3.3k
Avg merge
2d 2h
Merged PRs (30d)
91

Description

Issue type

Crash or freeze

Bug description

Any time I try to open a file (or save a file), it closes unexpectedly. It seems to be a glitch with the "file" dialog box. The crash happens shortly after the "file" box appears. It happens every time.
I'm using version 4.1.1.232071203, rev e4d1dff with Windows 10 Pro, version 22H2.
I had the same issue with version 4.1.0.231921402, rev 2e3a93a with Windows 10 Pro, version 22H2.

I had the same issue with version 3.6.2. In 3.6.2, was able to fix the problem by going to Edit>Preferences>Advanced and toggling ui/application/useNativeDialogs. I can't see how to toggle this setting in 4.1.0 or 4.1.1.

Does anyone have a suggestion or idea that I can try? I've gone back to 3.6.2 because I can't save my work or open a file.

Thanks for your help.

Steps to reproduce
  1. Open MuseScore
  2. Create a score
  3. Click "File">"Save"
  4. The file dialog box opens, then about three seconds later, the "MuseScore4.exe has stopped working" box opens

OR:

  1. Start MuseScore
  2. Click "File">"Open"
  3. The file dialog box opens, then about three seconds later, the "MuseScore4.exe has stopped working" box opens
Screenshots/Screen recordings

No response

MuseScore Version

OS: Windows 10 Version 2009 or later, Arch.: x86_64, MuseScore version (64-bit): 4.1.1-232071203, revision: github-musescore-musescore-e4d1ddf

Regression

Yes, this used to work in MuseScore 3.x and now is broken

Operating system

Windows 10 Pro, version 22H2

Additional context

Video file was too big to share.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.