Crash involving hidden staff popup

[ApocalypticSalad]

Issue type

Choose option...

Description with steps to reproduce

See comment

---

1. Have an instrument with more than one staff (e.g. create a solo piano score)
2. Enable "Automatically hide all empty staves"
3. Click on the All-Seeing Eye of Terpsichore
4. There might be drop-down arrows next to the individual piano staves (see image)
5. Click on one of these phantom arrows
6. On Windows, Musescore crashes immediately. On (my) Linux, Musescore freezes and a catastrophic memory leak springs up, rapidly filling RAM and the swap partition (a gigabyte every few seconds).

I say "might be", these arrows seem to exist around 50% of the time (whether making a new score as above, or opening the existing score I was working on) and I have no idea what the difference is. You might need to give it a few tries if you're trying to reproduce.
If the arrows don't exist then obviously you can't click them and so there's no crash.

Supporting files, videos and screenshots

In which versions of MuseScore Studio is this issue present?

4.6.3

Regression

I was unable to check

Operating system

Windows (10), Linux (Mint 22.1)

Additional context

No response

Checklist

• This report follows the guidelines for reporting bugs and issues
• I have verified that this issue has not been logged before, by searching the issue tracker for similar issues
• I have attached all requested files and information to this report
• I have attempted to identify the root problem as concisely as possible, and have used minimal reproducible examples where possible

[MarcSabatella]

I can confirm the crash on Linux. Sometimes it is instantaneous, sometimes it hangs. Not sure what those arrows next to the individual staves are meant to convey; there is nothing to expand. So probably it's a bug that they show in the first place.

[cbjeukendrup]

It's strange but I've not been able to reproduce this so far. I don't get the erroneous dropdown arrows. I've tried on macOS, Windows and Ubuntu.

[bkunda]

Thanks for reporting this. To help us identify the cause of the problem, could you please upload your log files here as a .zip file?

You can find your log files on Windows by opening MuseScore Studio, and going to Diagnostics > Save diagnostic files.

You can also access them directly at this location: C:\Users\YOURUSERNAME\AppData\Local\MuseScore\MuseScore4\logs.

[ApocalypticSalad]

These are my Linux ones. MuseScore_251119_232028.log hopefully will be helpful cause I did the crash.
sv.zip