System unresponsive after suspend (hibernate)

• Mar 18, 2011 - 12:44
Type
Functional
Severity
S5 - Suggestion
Status
closed
Project
MuseScore

When MuseScore (Linux) is running and the laptop is suspended to disk (/sys/power/state), the CPU usage of mscore jumps to 100% after resuming. I suppose there is some cyclic task trying to catch up with the cycles missed during standby.
Let me know if there is anything I can investigate.

Comments

• Mar 18, 2011 - 14:18

Does this happen every time for you? What version of MuseScore are you using? What operating system and version are you using? Does this ever happen when MuseScore is not running?

Reply

• Mar 18, 2011 - 14:23
Status (old) needs info ⇒ active

So far, this has always happened when I suspended the computer with MuseScore running.
I'm running the Arch Linux build of MuseScore 1.0 (musescore 1.0-1).
The problem does not occur when not running MuseScore, and a quick glance at "top" shows that the mscore process is eating the CPU.

Reply

• Mar 19, 2011 - 11:25

Portaudio is grayed in my settings page, although I have portaudio 19_20071207-3 (libportaudio.so.2.0.0) installed and jackd running.
It seems the Arch Linux build of MuseScore is built without portaudio support - do you have another idea?

Reply

• Mar 21, 2011 - 16:20
Status (old) needs info ⇒ active

I have reproduced this problem without suspend/resume:
1. Start MuseScore and load a file or two
2. killall -STOP mscore
3. Wait a while - at least 30 minutes for visible impact
4. killall -CONT mscore
-> MuseScore will lock up and eat the CPU for a while. For me, it was roughly one second for every minute of process suspension

This way, the problem should be reproducible on any Linux system using ALSA - and can also be tested on different output methods.

Reply