When using strace against scoperegistry in this state, the output gets
*flooded* with the following until I interrupt strace:
[pid 10491] futex(0x443a14, FUTEX_WAKE_PRIVATE, 1) = 0
[pid 10491] futex(0x443a3c, FUTEX_WAIT_BITSET_PRIVATE|FUTEX_CLOCK_REALTIME,
244392527, {633437444, 854775807}, ffffffff) = -1 ETIMEDOUT (Connection timed
out)
Now, googling for it reveals several problems like this (for various
programs) caused by the leap second (it so happens that leap seconds
were added on Jun 30/Jul 1 this year). Could this be the issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1470750
Title:
scoperegistry uses 45% CPU after applying updates from the store,
draining battery quickly
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1470750/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
