Multiple open scores create multiple Musescore processes.
Up to version 4.3.6, there was only one process. Each score had its own TAB.
Loading additional scores multiplies the amount of memory required, and the computer becomes slower and slower. I think this is a bug.
Comments
3.6.2, right, That changed with 4.0. It is not a bug, but by design
See https://github.com/musescore/MuseScore/issues/12647; it is currently by design, but we plan to change this.
In reply to See https://github.com… by cbjeukendrup
@cbjeukendrup I have read your comments on github and I’m super glad to have found a sensible and solid analysis of the situation and of what should/could be done.
It is conforting to see that a good software engineer has these issues into his hands.
I was disappointed with musescore 4 and upset with the answers from some musescore fan in this forum trying to convince us that « because musescore does it that way it is the only and good way »
Reading your comments gives me back hope in the future of musescore .