Project

General

Profile

action #17092

100% cpu usage in virtio_screen.pm function read_until

Added by nadvornik over 5 years ago. Updated about 5 years ago.

Status:
Resolved
Priority:
High
Assignee:
Category:
Concrete Bugs
Target version:
Start date:
2017-02-15
Due date:
% Done:

0%

Estimated time:
Difficulty:

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.

History

#1 Updated by rpalethorpe over 5 years ago

  • Priority changed from Normal to High

I guess we can set the socket to blocking and set a timer to signal a timeout or similar, I will do some research, it could be improved anyway.

#2 Updated by rpalethorpe over 5 years ago

  • Status changed from New to Feedback

I have made a patch which blocks using select. https://github.com/os-autoinst/os-autoinst/pull/724

#3 Updated by okurz over 5 years ago

  • Category set to Concrete Bugs
  • Target version set to Milestone 6

#4 Updated by okurz about 5 years ago

  • Status changed from Feedback to Resolved

merged, nadvornik proved it's working for him.

Also available in: Atom PDF