Actions
action #17092
closed100% cpu usage in virtio_screen.pm function read_until
Status:
Resolved
Priority:
High
Assignee:
Category:
Regressions/Crashes
Target version:
Start date:
2017-02-15
Due date:
% Done:
0%
Estimated time:
Description
On my machine isotovideo runs with 100% cpu usage in virtio_screen.pm function read_until.
strace shows that it cycles on this:
read(21, 0x6670db0, 2048) = -1 EAGAIN (Resource temporarily unavailable)
Adding usleep(1000) before the retry on EAGAIN (virtio_screen.pm line 197) helped, but maybe there is a better fix.
Actions