Huge CPU loading by whoopsie & NetworkManager tandem

Bug #1056393 reported by Nicholas Shatokhin
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Whoopsie
Invalid
Undecided
Unassigned

Bug Description

Sometimes I see huge loading by two this processes. And always its only together. NetworkManager loads CPU tiny without whoopsie by when whoopsie starts the hell begining.

ProblemType: Bug
DistroRelease: Ubuntu 12.04
Package: whoopsie 0.1.32
ProcVersionSignature: Ubuntu 3.2.0-30.48-generic 3.2.27
Uname: Linux 3.2.0-30-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu13
Architecture: i386
Date: Tue Sep 25 21:51:40 2012
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
SourcePackage: whoopsie-daisy
UpgradeStatus: Upgraded to precise on 2012-04-03 (174 days ago)

Revision history for this message
Nicholas Shatokhin (robotex) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in whoopsie-daisy (Ubuntu):
status: New → Confirmed
Revision history for this message
Gertjan (gjvde) wrote :

I believe the torrent program transmission-gt when it downloads a torrent gets the NetworkManager involved, and this somehow triggers the mentioned CPU load tandem. Firefox seems to have the same impact as transmission-gt, but overall firefox is probably less network intensive than transmission-gt.
On the system I have also seen whoopsie tandem with deja-dup-monito (untill i disabled deja-dup-monito).

Revision history for this message
Gertjan (gjvde) wrote :

Follow-up on #3: the problem is not triggered anymore. My internet connection was set to use ip4 and ip6. This in itself should not cause trouble, since also my adsl modem is set to both use ip4 and ip6.
But after disabling ip6 in the "Edit Connections .." dialog, the problem is not triggered anymore.

Evan (ev)
no longer affects: whoopsie-daisy (Ubuntu)
Revision history for this message
Evan (ev) wrote :

Closing as the reporter says this is no longer an issue.

Changed in whoopsie:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.