Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Busy loop in backendRunLoop (usb backend process hogs cpu) #2721

Closed
michaelrsweet opened this issue Feb 27, 2008 · 1 comment
Closed

Busy loop in backendRunLoop (usb backend process hogs cpu) #2721

michaelrsweet opened this issue Feb 27, 2008 · 1 comment
Labels
duplicate This issue or pull request already exists priority-medium
Milestone

Comments

@michaelrsweet
Copy link
Collaborator

Version: 1.3.2
CUPS.org User: jdarmochwal

I am using a Canon Pixma iP4300 with a proprietary driver and Cups 1.3.2 on a Linux PC.
When I start a print Job, a "gs" process (started by the printer driver) and a "usb" process each use about 50% of the cpu. The "usb" process obviously is in a busy loop, since there is no data ready to be sent to the printer.

That busy loop is the for-loop in backendRunLoop (backend/runloop.c)
In my case print_bytes is 0, side_cb is true, use_bc is false. The select call returns immediately, because output is ready. But since no data is available the loop just goes round and round.
I guess doing a select call just on the input file descriptors before the current select call would help.

@michaelrsweet
Copy link
Collaborator Author

CUPS.org User: mike

Dupe of STR #2664, already fixed in CUPS 1.3.6...

@michaelrsweet michaelrsweet added priority-medium duplicate This issue or pull request already exists labels Mar 17, 2016
@michaelrsweet michaelrsweet added this to the Stable milestone Mar 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
duplicate This issue or pull request already exists priority-medium
Projects
None yet
Development

No branches or pull requests

1 participant