** Changed in: ubuntu-push
Status: Fix Committed = Fix Released
** Changed in: ubuntu-push (Ubuntu)
Status: In Progress = Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This has been worked around on the server until we can release a client
that works around the timing issue with the library.
** Changed in: ubuntu-push
Assignee: (unassigned) = John Lenton (chipaca)
** Changed in: ubuntu-push
Importance: Undecided = Critical
** Changed in: ubuntu-push
** Package changed: ubuntu-push-client (Ubuntu) = ubuntu-push (Ubuntu)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage
** Also affects: ubuntu-push
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage
** Changed in: ubuntu-push-client (Ubuntu)
Status: Confirmed = In Progress
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
log filled with this:
2014/04/17 15:24:28.758872 DEBUG Connected 91.189.92.115:443.
2014/04/17 15:24:28.759361 DEBUG Session connected after 1 attempts
2014/04/17 15:24:28.785957 ERROR session exited: EOF
2014/04/17 15:24:28.786721 DEBUG trying to connect to: 91.189.92.115:443
2014/04/17
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: ubuntu-push-client (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
On manta its using 15-20% CPU
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage notifications about this bug go to:
fwiw pinging push-delivery.ubuntu.com gets no response, but I don't know
the configuration as to whether it should reply
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
We're shutting down the service over the weekend top stop the battery
drain. Have been tracking this one down all day, but didn't realise
(didn't stop to think!) how bad an impact on cpu usage / battery it
would have.
After the weekend we'll be able to get workarounds in place.
--
You received
Yikes.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage notifications about this bug go to:
So, there's two client-side bugs. One is that, once a connection is
successful, it resets the exponential back-off mechanism, so the server
dropping the connection hard every time gets it in a spinlock. That's
lp:1309231.
The other is that the whoopsie identifier we get is nil for the first
~10
Into a spin, not a spinlock.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1309152
Title:
ubuntu-push-client consuming a lot of CPU after boot
To manage notifications about this bug go to:
13 matches
Mail list logo
