ubuntu one uses 99%cpu for two days

[Krister Swenson]

I chose a directory with 1.8 GB of data to sync with ubuntu one.
Not only is the bandwidth utilization extremely low (I have no limit set), but the cpu has been highly utilized for many days now.

More information to come...
---
Architecture: i386
DistroRelease: Ubuntu 10.04
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release i386 (20100429)
NonfreeKernelModules: nvidia
Package: ubuntuone-client 1.2.1-0ubuntu2
PackageArchitecture: all
ProcEnviron:
 LANGUAGE=
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-22.33-generic 2.6.32.11+drm33.2
Tags: lucid
UbuntuOneClientConfig:
 [ubuntuone]
 connected = True
 connect = 0
 show_applet = 0
 bookmarked = True
UbuntuOneSyncdaemonExceptionsLog:

UbuntuOneUserSyncdaemonConfig:
 [bandwidth_throttling]
 read_limit = 2097152
 write_limit = 2097152
 on = False
Uname: Linux 2.6.32-22-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Krister Swenson (thekswenson)]

apport information

[Krister Swenson (thekswenson)]

apport information

[Krister Swenson (thekswenson)]

apport information

[Krister Swenson (thekswenson)]

apport information

[Krister Swenson (thekswenson)]

Attached are some logs from ~/.cache/ubuntuone/log

[Joshua Hoover (joshuahoover)]

Hi Krister,

Thank you for following up with this bug report from the forum thread! I'm going to have a developer look into your log files to see if we can tell what the cause of the problem might be.

Thank you,

Joshua

[John O'Halloran (john-oh)]

I have also encountered this problem on a couple of occasions. From the forums there have been others. I started to follow Joshua's instructions to Krister in the forum. The ubuntuone-syncdaemon shutdown and when restarted it was using much less CPU time. I'm new to Lunchpad but if there's anything I can do to help fix this bug please let me know.

[Leo Arias (elopio)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 913912, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.