I have now followed my suspect what can have caused the 100%-CPU issue
in cups-browsed, that there was a global HTTP connection and it was used
by paralalizing threads. So I have done away with the global HTTP
connection:
https://github.com/OpenPrinting/cups-browsed/commit/a8b645e4b3
I have done a regression test by running make check, which is running
cups-browsed with emulated network printers and also sending jobs
through the auto-created queues.
As the bug is not easily reproducible, occurs only sporadically, the
change has to be tried out. I will make it available in packages soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/2049315
Title:
cups-browsed running non-stop on two cores
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2049315/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
