[Touch-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
i have problem on ubuntu 15.04 with both unity-panel-service(812MB) AND indicator-power-service (1.2GB) lop@work:/tmp$ pmap -X 9299 | head 9299: /usr/lib/x86_64-linux-gnu/indicator-power/indicator-power-service Address Perm Offset DeviceInodeSize Rss Pss Referenced Anonymous Swap Locked Mapping 0040 r-xp 08:01 16779454 104 76 76 76 0 0 0 indicator-power-service 00619000 r--p 00019000 08:01 16779454 4 4 4 4 4 0 0 indicator-power-service 0061a000 rw-p 0001a000 08:01 16779454 4 4 4 4 4 0 0 indicator-power-service 021c3000 rw-p 00:000 1109876 1102164 1102164 935284 1102164 7588 0 [heap] 7ff8b800 rw-p 00:000 25396 25396 25396 10212 25396 0 0 lop@work:/tmp$ pmap -X 9248 | head 9248: /usr/lib/unity/unity-panel-service Address Perm Offset DeviceInodeSizeRssPss Referenced Anonymous Swap Locked Mapping 0040 r-xp 08:01 16518994 72 64 64 64 0 0 0 unity-panel-service 00611000 r--p 00011000 08:01 16518994 4 0 0 0 0 4 0 unity-panel-service 00612000 rw-p 00012000 08:01 16518994 4 4 4 4 4 0 0 unity-panel-service 00f76000 rw-p 00:000 682640 554360 554360 419812 554360 128172 0 [heap] 7f927800 rw-p 00:000 21680 21680 21680 12900 21680 0 0 lop@work:/tmp$ dpkg -l | egrep ^ii | egrep -o indicator-\\S* indicator-application indicator-appmenu indicator-bluetooth indicator-keyboard indicator-messages indicator-multiload indicator-power indicator-printers indicator-session indicator-sound any workaround? Thanks Mauro -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to unity in Ubuntu. https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Released Status in Application Menu Indicator 13.10 series: Fix Released Status in The Ubuntu Power Consumption Project: Fix Released Status in Unity: Invalid Status in Ubuntu: Fix Released Status in indicator-appmenu package in Ubuntu: Fix Released Status in unity package in Ubuntu: Invalid Status in The Saucy Salamander: Fix Released Status in indicator-appmenu source package in Saucy: Fix Released Bug description: Impact: high CPU/memory usage from unity-panel-service Test case: Open a large image in the GIMP and activate a lot of items from the global menu. Using shortcuts is enough and faster to reproduce this bug (I've always used Ctrl+A and Ctrl+Shift+A). Memory usage of unity- panel-service increases steadily and it uses a lot of CPU shortly after activating the menu items in a short time. Regression potential: check that the menus are stable/working as they should - Just going about my business on Ubuntu Raring amd64 on an x230 and I heard the fan kick into action. top showed me that unity-panel-service was consuming all the free cycles on one of my CPUs. I killed it before my machine overheated, so I didn't attach a debugger to see why it was totally pegging out a CPU. I'm not sure if this adds any context, but I was using a LibreOffice spreadsheet and I could not insert a table because the menu had lost it's mind, and then I observed the overly loaded CPU a very short while after that. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-appmenu/+bug/1199877/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1455900] [NEW] package whoopsie 0.2.47 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100
Public bug reported: after upgrade 14.10 to 15.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: whoopsie 0.2.47 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashReports: 640:0:110:1101209:2015-05-17 01:04:13.422432422 +0200:2015-05-17 01:04:14.422432422 +0200:/var/crash/whoopsie.0.crash 640:0:110:18692:2015-05-17 13:04:15.679931436 +0200:2015-05-17 13:04:15.679931436 +0200:/var/crash/_usr_bin_add-apt-repository.0.crash Date: Sun May 17 01:04:10 2015 DuplicateSignature: package:whoopsie:0.2.47:subprocess new pre-removal script returned error exit status 100 ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationDate: Installed on 2013-09-04 (619 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.47 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-05-17 (0 days ago) ** Affects: whoopsie (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package autoreport-false dist-upgrade vivid -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to whoopsie in Ubuntu. https://bugs.launchpad.net/bugs/1455900 Title: package whoopsie 0.2.47 failed to install/upgrade: subprocess new pre- removal script returned error exit status 100 Status in whoopsie package in Ubuntu: New Bug description: after upgrade 14.10 to 15.04 ProblemType: Package DistroRelease: Ubuntu 15.04 Package: whoopsie 0.2.47 Uname: Linux 4.1.0-040100rc2-generic x86_64 ApportVersion: 2.17.2-0ubuntu1 Architecture: amd64 CrashReports: 640:0:110:1101209:2015-05-17 01:04:13.422432422 +0200:2015-05-17 01:04:14.422432422 +0200:/var/crash/whoopsie.0.crash 640:0:110:18692:2015-05-17 13:04:15.679931436 +0200:2015-05-17 13:04:15.679931436 +0200:/var/crash/_usr_bin_add-apt-repository.0.crash Date: Sun May 17 01:04:10 2015 DuplicateSignature: package:whoopsie:0.2.47:subprocess new pre-removal script returned error exit status 100 ErrorMessage: subprocess new pre-removal script returned error exit status 100 InstallationDate: Installed on 2013-09-04 (619 days ago) InstallationMedia: Ubuntu 13.04 Raring Ringtail - Release amd64 (20130424) RelatedPackageVersions: apport-noui N/A SourcePackage: whoopsie Title: package whoopsie 0.2.47 failed to install/upgrade: subprocess new pre-removal script returned error exit status 100 UpgradeStatus: Upgraded to vivid on 2015-05-17 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/whoopsie/+bug/1455900/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1312051] Re: Upstart init process consuming all ram
I confirm this, after 16 days of uptime on ubuntu 14.10 desktop, the process upstart use 1,8 GB of memory. lop@work:~$ ps aux | grep upstart --user lop 7656 0.1 22.9 2218984 1851736 ? Ss apr07 9:14 upstart --user Any workaround? i don't have any unity-greeter-session-broadcast installed Regards -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to upstart in Ubuntu. https://bugs.launchpad.net/bugs/1312051 Title: Upstart init process consuming all ram Status in upstart package in Ubuntu: Confirmed Bug description: In Ubuntu 14.04 amd64 Upstart init process keeps growing in ram. It's about 0.1 MiB every 10s. ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: upstart 1.12.1-0ubuntu4 ProcVersionSignature: Ubuntu 3.13.0-24.46-generic 3.13.9 Uname: Linux 3.13.0-24-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.14.1-0ubuntu3 Architecture: amd64 CurrentDesktop: Unity Date: Thu Apr 24 10:33:58 2014 InstallationDate: Installed on 2011-09-05 (961 days ago) InstallationMedia: Ubuntu 11.10 Oneiric Ocelot - Beta amd64 (20110901) ProcKernelCmdline: BOOT_IMAGE=/boot/vmlinuz-3.13.0-24-generic root=/dev/mapper/hostname-root ro quiet splash zswap.enabled=1 crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M crashkernel=384M-:128M SourcePackage: upstart UpgradeStatus: Upgraded to trusty on 2014-02-07 (75 days ago) UpstartBugCategory: System UpstartRunningSessionVersion: init (upstart 1.12.1) UpstartRunningSystemVersion: init (upstart 1.12.1) modified.conffile..etc.NetworkManager.NetworkManager.conf: [modified] modified.conffile..etc.at.deny: [inaccessible: [Errno 13] Permission denied: '/etc/at.deny'] modified.conffile..etc.dconf.db.gdm: [modified] modified.conffile..etc.default.cups: [modified] modified.conffile..etc.default.whoopsie: [modified] modified.conffile..etc.iscsi.iscsid.conf: [modified] mtime.conffile..etc.NetworkManager.NetworkManager.conf: 2013-12-20T12:14:24.844783 mtime.conffile..etc.dconf.db.gdm: 2014-02-21T11:46:26.072553 mtime.conffile..etc.default.cups: 2014-03-11T16:01:34.805892 mtime.conffile..etc.default.whoopsie: 2013-10-23T11:36:50.678661 mtime.conffile..etc.iscsi.iscsid.conf: 2013-07-10T17:05:34.637955 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/upstart/+bug/1312051/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
