Crash city
I have no scores open besides this one. It almost immediately (I am in the process of adding lyrics) consumes 100% cpu (Mac OSX latest) and become minimally responsive, then unresponsive and I have to kill the process. This has happened 3 or 4 times in the last hour, and I can't edit this score.
I have not used the Piano Roll Editor, and I have the play panel (see other report) and inspector open.
| Attachment | Size |
|---|---|
| Confiteor232.mscz | 40.39 KB |
Comments
No problem here, Windows 7
No problems here either. If you can come up with precise steps to reproduce what you are seeing, please post them.
Do you have the Navigator open? A couple of people have reported performance issues with that. I can't reproduce any problem with your score with or without the Navigator though.
In reply to No problems here either. If by Marc Sabatella
Yes, I do have the navigator open, and I saw funnies in it when I went into Continuous Scroll mode, try that --- (I am on El Capitan latest).
What % cpu in Activity Monitor should I see with nothing but this score open?
In reply to Yes, I do have the navigator by [DELETED] 1831606
For me it seems to vary between about 3% (when not active) up to about 20% while editing, which drops again to to about 3% after a few seconds.
In reply to For me it seems to vary by Isaac Weiss
I'm seeing 101%. Something is very broken. I'm going to have to kill it and rename that file so I can get in to experiment.
I'm not encountering any problems with it with MuseScore 2.0.3 on El Capitan 10.11.3. Any specific measure where entering lyrics makes MuseScore stop responding?
In reply to I'm not encountering any by Isaac Weiss
I have done nothing at all after reopening the crashed app. I switch applications to Firefox. I switched back to MuseScore and the app is unresponsive (the play panel exposes, but not the ain window). I have done nothing at all.
I use "show play panel at startup." Maybe that is part of it?
In reply to I have done nothing at all by [DELETED] 1831606
It's the Navigator. I unviewed the Navigator and CPU went down to single digits. Expose the navigator, read in that score and look at CPU consumption in the Activity Monitor.
In reply to It's the Navigator. I by [DELETED] 1831606
Now, that's interesting. With the Navigator it does go to about 100% CPU, but response only slightly slows down.
In reply to Now, that's interesting. With by Isaac Weiss
Wait five minutes, visit another app, and you won't be able to get back in.
In reply to I have done nothing at all by [DELETED] 1831606
FWIW, I have both Play Panel and Navigator open, and am watching my task manager, and I don't see any unusual activity - it stays around 1% for me. That's on Ubuntu. So maybe a Mac only issue - or maybe there are other variables involved?
In reply to FWIW, I have both Play Panel by Marc Sabatella
On that score?
In reply to On that score? by [DELETED] 1831606
Yes. But there are a couple of other reports from people on Linux who are also seeing some sort of slowdown. Not clear if it's related to what you are seeing or not. But so far, I haven't been able to reproduce any performance issues.
In reply to Yes. But there are a couple by Marc Sabatella
Try scroll-view mode on both platforms on this score. Scroll around, change a note or two and see if chaos breaks loose.
In reply to Try scroll-view mode on both by [DELETED] 1831606
You mean Continuous View? I tried it, scrolled, changed some notes - no obvious issues of any kind.
In reply to You mean Continuous View? I by Marc Sabatella
Yeah. I look forward to a Mac trial --- It behaved in a visibly broken fashion --
Running an 8-core Mac Pro tower with 18GB of RAM here, was using Musescore 2.0.3 most of the day, (with navigator open) and it was acting normally and performing fine. Suddenly performance just became horribly bad / unusable. Restarted Musescore, problem was present again as soon as I opened a score.
It does *not* seem to matter which score I open or how large/small it is.
Rebooted the computer completely, same issue after restart.
Mentioned it in the freenode IRC channel, Marc said to turn off navigator and see if the problem went away. It does. He asked me to add some specifics here.
Note: I was using navigator (as I always have) and it was fine. Then suddenly it became unusable. I can't come up with any explanation for why that might be the case.
I noticed that if I do note audio playback now after turning navigator back on, the note 'sticks' and plays continuously until I turn off navigator again, even more strange.
All menus are 'laggy' inside the program while navigator is enabled. Even if I minimize the Musescore app itself, top (or any other load monitor) shows very high usage for musescore. The rest of the system and any other running apps work normally.
As bizarre as all that sounds, hopefully it is helpful to pinning it down.
In reply to Running an 8-core Mac Pro by randy.howard.1675
Could it be that you resized the navigator before it went bad. If you don't have any preferences set, you can try to go to Help > Revert to factory settings, and see if the problem persists.
In reply to Could it be that you resized by [DELETED] 5
I'm not eager to lose all my settings. If there were a way to save and restore this, I might try. I didn't know the navigator could be resized, but opening and closing the inspector might do just that. I think it started the first time I switched into "Continuous mode", in which it misbehaved frighteningly (loops of flashing renderings).
In reply to I'm not eager to lose all my by [DELETED] 1831606
You can backup your old settings, you'd find them in %LOCALAPPDATA%\MuseScore\ /(plugins, translatations, palettes, shortcuts) and %APPDATA%\MuseScore\MuseScore2.ini
In reply to Could it be that you resized by [DELETED] 5
Interesting. I never realized the Navigator was even resizable. I just turned it back on and made it slightly larger, and the performance problems seems to be gone again.
Then I shrunk it back down (although I probably didn't get the exact same dimensions again) and it still seems to be running okay.