Bug#704888: gpodder: Causes 100% cpu load for several minutes
Package: gpodder Version: 3.5.0-1 Followup-For: Bug #704888 Hi, I just had to kill gpodder again, as it again hung itself up, causing 100% CPU load after I had clicked on Download in the dialogue for downloading new episodes. A mere 3 new episodes were avaible for download. However, after clicking the button, the dialogue does not go away, cpu load shoots up to 100% and stays there. After 10 minutes or so, I killed the programme. There is nothing in the log files. The last log entry is two hours old. Thanks, Johannes -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpodder depends on: ii python 2.7.3-4 ii python-dbus 1.1.1-1 ii python-feedparser 5.1.2-1 ii python-gtk2 2.24.0-3+b1 ii python-mygpoclient 1.4-1 ii python-support 1.0.15 ii python-webkit 1.1.8-2 Versions of packages gpodder recommends: ii dbus-x11 1.6.8-1 ii libqtwebkit-qmlwebkitplugin 2.2.1-5 ii python-gst0.10 0.10.22-3 ii python-simplejson2.5.2-1 Versions of packages gpodder suggests: ii gnome-bluetooth 3.4.2-1 ii mplayer 3:1.1-dmo9 ii python-eyed3 0.6.18-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704888: gpodder: Causes 100% cpu load for several minutes
Package: gpodder Version: 3.5.0-1 Followup-For: Bug #704888 It is no different on both versions. It seems, the 100% CPU load mostly occurs when gpodder.net is down and gpodder tries to sync. Unfortunately, gpodder.net's downtimes are quite frequent.. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpodder depends on: ii python 2.7.3-4 ii python-dbus 1.1.1-1 ii python-feedparser 5.1.2-1 ii python-gtk2 2.24.0-3+b1 ii python-mygpoclient 1.4-1 ii python-support 1.0.15 ii python-webkit 1.1.8-2 Versions of packages gpodder recommends: ii dbus-x11 1.6.8-1 ii libqtwebkit-qmlwebkitplugin 2.2.1-5 ii python-gst0.10 0.10.22-3 ii python-simplejson2.5.2-1 Versions of packages gpodder suggests: ii gnome-bluetooth 3.4.2-1 ii mplayer 3:1.1-dmo9 ii python-eyed3 0.6.18-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#704888: gpodder: Causes 100% cpu load for several minutes
Hi, Can you reproduce this with gPodder 3.5.0 from Debian unstable after removing your database and downloads? If so, do the logfiles (~/gPodder/Logs/) show anything unusual? Thanks, Thomas 2013/4/7 Johannes Rohr jor...@gmail.com Package: gpodder Version: 2.20.1-1 Severity: normal Recently, feed updates and downloads of episodes have started causing 100% for several minutes, during which the programme becomes unresponsive. I first observed this behaviour on gpodder 3.5 from sid. Therefore I downgraded to the version from Wheezy, deleted the entire configuration and re-synced with gpodder.net, but to no avail. This makes the programme unusable for any practical purpose. Please let me know what specific debug information is needed and how it can be extracted. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpodder depends on: ii python 2.7.3-4 ii python-dbus 1.1.1-1 ii python-feedparser 5.1.2-1 ii python-gtk2 2.24.0-3+b1 ii python-mygpoclient 1.4-1 ii python-support 1.0.15 Versions of packages gpodder recommends: ii dbus-x11 1.6.8-1 ii python-gpod0.8.2-7 ii python-gst0.10 0.10.22-3 ii python-pymtp 0.0.4-4 ii python-simplejson 2.5.2-1 ii python-webkit 1.1.8-2 Versions of packages gpodder suggests: ii gnome-bluetooth 3.4.2-1 ii mplayer 3:1.1-dmo9 ii python-eyed3 0.6.18-1 -- no debconf information
Bug#704888: gpodder: Causes 100% cpu load for several minutes
Package: gpodder Version: 2.20.1-1 Severity: normal Recently, feed updates and downloads of episodes have started causing 100% for several minutes, during which the programme becomes unresponsive. I first observed this behaviour on gpodder 3.5 from sid. Therefore I downgraded to the version from Wheezy, deleted the entire configuration and re-synced with gpodder.net, but to no avail. This makes the programme unusable for any practical purpose. Please let me know what specific debug information is needed and how it can be extracted. -- System Information: Debian Release: 7.0 APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (450, 'experimental') Architecture: amd64 (x86_64) Foreign Architectures: i386 Kernel: Linux 3.2.0-4-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages gpodder depends on: ii python 2.7.3-4 ii python-dbus 1.1.1-1 ii python-feedparser 5.1.2-1 ii python-gtk2 2.24.0-3+b1 ii python-mygpoclient 1.4-1 ii python-support 1.0.15 Versions of packages gpodder recommends: ii dbus-x11 1.6.8-1 ii python-gpod0.8.2-7 ii python-gst0.10 0.10.22-3 ii python-pymtp 0.0.4-4 ii python-simplejson 2.5.2-1 ii python-webkit 1.1.8-2 Versions of packages gpodder suggests: ii gnome-bluetooth 3.4.2-1 ii mplayer 3:1.1-dmo9 ii python-eyed3 0.6.18-1 -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
