Overload CPU to 50% when this score is loaded
Hello,
MuseScoreNightly-2013-01-03-1723-eb2f71a on windows 7.
MuseScore use 50% of CPU when this score is loaded and doing nothing
Score attached is loaded on MuseScore Sheet Music
Bye
Robert
Attachment | Size |
---|---|
Toccata_et_Fuga.mscz | 35.91 KB |
Comments
I can't really confirm this. On XP pro SP3, Dualcore, nightly.exe goes up to 50% load for less than a second.
35650ee, from yesterday. And not with the new eb2f71a either
Image attached
Corel paint shop pro at 45% is only for snapshot. With or without, CPU used is the same.
Is your Navigator at a particular height where it can't decide between showing the scroll bar and not? Adjust it (up or down) and see if the CPU usage changes. This is a known bug.
I didn't mean to say that I don't believe you, just that it doesn't happen on my PC, which is quite a few years old, so not the fastest.
#15136: [trunk] Navigator gets into redraw loop?
At least that I can still reproduce, and with your score.
don't worry ;-). it's not for your remark but it's that an image is better than 1000 words.
Robert
Ok, it's that.
Closing MuseScore connect or resize it reduce CPU usage.
I never have this issue before.
Thank's
;-)
Is it a duplicate of the one we've mentioned above?
It only happens when the width of the pages in the navigator is almost exactly the same as the width of the navigator window (slightly smaller or slightly larger). It's not common, and only adjusting the height (or width) of navigator fixes it. That's why removing the Connect window also fixed it as the navigator is much wider. So if you have a taller navigator, but less pages in the score, you can still trigger the bug.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.
Automatically closed -- issue fixed for 2 weeks with no activity.