[Dx-packages] [Bug 1308130] [NEW] indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
Public bug reported:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling every
4 seconds is a little bit heavy handed IMHO.
** Affects: indicator-messages (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
New
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1308130] Re: indicator-messages-service is waking up every 4 seconds adding inotifies on paths that don't exist
This shows up in the daily testing too:
http://ci.ubuntu.com/power/eventstat/image/3138/machine/6/task
/indicator-messages-service/details/
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to indicator-messages in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1308130
Title:
indicator-messages-service is waking up every 4 seconds adding
inotifies on paths that don't exist
Status in “indicator-messages” package in Ubuntu:
New
Bug description:
I've observed that an idle indicator-messages-services is waking up
every 4 seconds on a poll() and doing two inotify_add_watch() calls on
paths that don't exist, which wastes power on devices such as phones.
strace shows:
clock_gettime(CLOCK_MONOTONIC, {10117, 224455428}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3991) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10121, 224516469}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10121, 232085521}) = 0
poll([{fd=8, events=POLLIN}, {fd=9, events=POLLIN}], 2, 3984) = 0 (Timeout)
clock_gettime(CLOCK_MONOTONIC, {10125, 222593684}) = 0
inotify_add_watch(9, /usr/local/share/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
inotify_add_watch(9, /usr/share/ubuntu-touch/applications,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
clock_gettime(CLOCK_MONOTONIC, {10125, 229094524}) = 0
Can these redundant polling checks be reduced or removed? Polling
every 4 seconds is a little bit heavy handed IMHO.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/indicator-messages/+bug/1308130/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a poll loop
** Summary changed: - hud-service is eating up 100% of one of my CPUs in a pool loop + hud-service is eating up 100% of one of my CPUs in a poll loop -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a poll loop Status in Unity HUD: Fix Committed Status in “hud” package in Ubuntu: In Progress Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33
[Dx-packages] [Bug 1300722] [NEW] hud-service is eating up 100% of one of my CPUs in a pool loop
Public bug reported: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #35 0x7fda833dc048 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ProblemType: Bug DistroRelease: Ubuntu 14.04 Package: hud 13.10.1+14.04.20140326-0ubuntu1 ProcVersionSignature: Ubuntu 3.13.0-20.42-generic 3.13.7 Uname: Linux 3.13.0-20-generic x86_64 ApportVersion: 2.14-0ubuntu1 Architecture: amd64 CurrentDesktop: Unity Date: Tue Apr 1 12:23:11 2014 EcryptfsInUse: Yes InstallationDate: Installed on
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a pool loop
Hi Pete, how do I look that up? -- You received this bug notification because you are a member of DX Packages, which is subscribed to hud in Ubuntu. https://bugs.launchpad.net/bugs/1300722 Title: hud-service is eating up 100% of one of my CPUs in a pool loop Status in “hud” package in Ubuntu: New Bug description: hud-service is polling like crazy: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 2295 hud-service 46084.6342.94 46127.58 (very high) 2325 hud-service 0.09 0.00 0.09 (very low) 2329 hud-service 0.07 0.00 0.07 (very low) 2340 hud-service 0.05 0.00 0.05 (very low) Total 46084.8442.94 46127.78 File I/O operations: No file I/O operations detected. System calls traced: PID Process Syscall CountRate/Sec 2295 hud-service poll 83 23124.8503 2295 hud-service write10 0.2313 2295 hud-service sendmsg 4 0.0925 2325 hud-service restart_syscall 1 0.0231 2329 hud-service restart_syscall 1 0.0231 2340 hud-service restart_syscall 1 0.0231 Total 100 23125.2435 (gdb) where #0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3 #5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #8 0x7fda83eb940b in DBusMenuImporter::slotMenuAboutToShow() () from /usr/lib/x86_64-linux-gnu/libdbusmenu-qt5.so.2 #9 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #10 0x0045ab3f in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #11 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #12 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #13 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #14 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #15 0x0045abd8 in hud::service::DBusMenuCollector::openMenu(QMenu*, unsigned int) () #16 0x0045ae8d in hud::service::DBusMenuCollector::activate() () #17 0x00441e43 in hud::service::WindowImpl::activate() () #18 0x00439f6a in hud::service::QueryImpl::updateToken(QSharedPointerhud::service::Window) () #19 0x0043a672 in hud::service::QueryImpl::refresh() () #20 0x0044b115 in ?? () #21 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #22 0x0045662a in hud::service::ApplicationListImpl::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #23 0x7fda8435d2a6 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #24 0x00467361 in ComCanonicalUnityWindowStackInterface::FocusedWindowChanged(unsigned int, QString const, unsigned int) () #25 0x004678bd in ?? () #26 0x00467c63 in ComCanonicalUnityWindowStackInterface::qt_metacall(QMetaObject::Call, int, void**) () #27 0x7fda82cf180f in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5 #28 0x7fda8435e22e in QObject::event(QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #29 0x7fda823d5c2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #30 0x7fda823dadf6 in QApplication::notify(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Widgets.so.5 #31 0x7fda84335c2d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #32 0x7fda84337e07 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #33 0x7fda84382cd3 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 #34 0x7fda833dbe04 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
[Dx-packages] [Bug 1300722] Re: hud-service is eating up 100% of one of my CPUs in a pool loop
What I am seeing is the following poll:
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 18813) = 1 ([{fd=13, revents=POLLIN}])
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(3, \1\0\0\0\0\0\0\0, 8) = 8
write(2, \33[31mvoid DBusMenuImporter::slot..., 335) = 335
write(2, \33[31mbool DBusMenuImporterPrivat..., 300) = 300
write(2, \33[31mvoid DBusMenuImporter::slot..., 115) = 115
sendmsg(13, {msg_name(0)=NULL, msg_iov(2)=[{l\1\0\1
\0\0\0\354\243\2\0r\0\0\0\1\1o\0\33\0\0\0/com/can..., 136},
{n\3\0\0\6\0\0\0opened\0\1s\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0, 32}],
msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 168
sendmsg(13, {msg_name(0)=NULL,
msg_iov(2)=[{l\1\0\1\4\0\0\0\355\243\2\0w\0\0\0\1\1o\0\33\0\0\0/com/can...,
136}, {\f\2\0\0, 4}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 140
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 25000) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
poll([{fd=13, events=POLLIN}], 1, 24999) = 1 ([{fd=13, revents=POLLIN}])
.. and this repeats and the timeout drops from 25000 milliseconds down
to 1, which is a tad excessive. Polling a gazillion times with sub
millisecond timeout is a little bit antisocial ;-)
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to hud in Ubuntu.
https://bugs.launchpad.net/bugs/1300722
Title:
hud-service is eating up 100% of one of my CPUs in a pool loop
Status in “hud” package in Ubuntu:
New
Bug description:
hud-service is polling like crazy:
Context Switches:
PID ProcessVoluntary Involuntary Total
Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec
2295 hud-service 46084.6342.94 46127.58 (very high)
2325 hud-service 0.09 0.00 0.09 (very low)
2329 hud-service 0.07 0.00 0.07 (very low)
2340 hud-service 0.05 0.00 0.05 (very low)
Total 46084.8442.94 46127.78
File I/O operations:
No file I/O operations detected.
System calls traced:
PID Process Syscall CountRate/Sec
2295 hud-service poll 83 23124.8503
2295 hud-service write10 0.2313
2295 hud-service sendmsg 4 0.0925
2325 hud-service restart_syscall 1 0.0231
2329 hud-service restart_syscall 1 0.0231
2340 hud-service restart_syscall 1 0.0231
Total 100 23125.2435
(gdb) where
#0 0x7fda8121cfbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1 0x7fda7f1bb4b8 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#2 0x7fda7f1ba3ff in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#3 0x7fda7f1a49dc in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#4 0x7fda7f1a5464 in ?? () from /lib/x86_64-linux-gnu/libdbus-1.so.3
#5 0x7fda82ce9e65 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#6 0x7fda82d2fc64 in ?? () from /usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#7 0x7fda82d30582 in QDBusPendingCallWatcher::waitForFinished() () from
/usr/lib/x86_64-linux-gnu/libQt5DBus.so.5
#8 0x7fda83eb940b in
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
** Changed in: ubuntu-power-consumption Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages 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 “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: Fix Released Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1234289] Re: accounts-daemon is progressively causing more wakeups over time
** Changed in: ubuntu-power-consumption Status: New = Fix Released -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1234289 Title: accounts-daemon is progressively causing more wakeups over time Status in The Ubuntu Power Consumption Project: Fix Released Status in “accountsservice” package in Ubuntu: Fix Released Bug description: Over the past few months accounts-daemon has been increasing the number of wakeup events it generates, see: http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task /accounts-daemon/details/ In April 2013 it was averaging about 13.5 wakeups per minute, now it has increased to 17.5. This isn't much overall, but it does seem like the trend is upwards and every wakeup takes the CPU out of deep sleep and hence consumes a little more power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1234289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1234289] Re: accounts-daemon is progressively causing more wakeups over time
running strace on one of the treads shows the culprit:
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3998) = 0 (Timeout)
inotify_add_watch(8, /etc/gdm,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3996) = 0 (Timeout)
inotify_add_watch(8, /etc/gdm,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
poll([{fd=4, events=POLLIN}, {fd=8, events=POLLIN}], 2, 3996) = 0 (Timeout)
inotify_add_watch(8, /etc/gdm,
IN_MODIFY|IN_ATTRIB|IN_CLOSE_WRITE|IN_MOVED_FROM|IN_MOVED_TO|IN_CREATE|IN_DELETE|IN_DELETE_SELF|IN_MOVE_SELF|IN_UNMOUNT|IN_ONLYDIR)
= -1 ENOENT (No such file or directory)
for some reason it is polling every 4 seconds and adding a watch on a
non-existent /etc/gdm directory
** Package changed: accountsservice (Ubuntu) = ubuntu-power-consumption
** Also affects: accountsservice (Ubuntu)
Importance: Undecided
Status: New
** Changed in: accountsservice (Ubuntu)
Importance: Undecided = Low
--
You received this bug notification because you are a member of DX
Packages, which is subscribed to accountsservice in Ubuntu.
Matching subscriptions: dx-packages
https://bugs.launchpad.net/bugs/1234289
Title:
accounts-daemon is progressively causing more wakeups over time
Status in The Ubuntu Power Consumption Project:
New
Status in “accountsservice” package in Ubuntu:
New
Bug description:
Over the past few months accounts-daemon has been increasing the
number of wakeup events it generates, see:
http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task
/accounts-daemon/details/
In April 2013 it was averaging about 13.5 wakeups per minute, now it
has increased to 17.5. This isn't much overall, but it does seem like
the trend is upwards and every wakeup takes the CPU out of deep sleep
and hence consumes a little more power.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu-power-consumption/+bug/1234289/+subscriptions
--
Mailing list: https://launchpad.net/~dx-packages
Post to : dx-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~dx-packages
More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1221871] Re: indicator-power-service is a lightly busy all the time
@Charles, 1. Is there a .deb I can test to verify this? 2. the i386 latest build of heath-check now does system call tracing correctly, so that may be helpful for checking the fix. Colin -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1221871 Title: indicator-power-service is a lightly busy all the time Status in The Power Indicator: Fix Committed Status in “indicator-power” package in Ubuntu: Triaged Bug description: In a vain attempt to reduce power on these phone devices I noticed that indicator-power-service is using just under 1% of one CPU all the time. CPU usage: PID ProcessUSR% SYS% TOTAL% 1358 indicator-power-serv 0.05 0.04 0.08 (very light load) It seems to be waiting on poll() on a couple of threads which cumulatively add up to about 1.68 wakeups a second over a 1 hour analysis: Top polling system calls: PID 1369 indicator-power-serv poll1.3462 polls/sec 1358 indicator-power-serv poll0.3376 polls/sec Total 1.6838 polls/sec This contributes to a bunch of context switching by these threads: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 1369 indicator-power-serv10.75 0.1510.90 (moderate) 1358 indicator-power-serv 3.53 0.07 3.60 (low) 1372 indicator-power-serv 0.00 0.00 0.00 (idle) Total 14.29 0.2214.50 [ See the attached log, launchpad formatting sucks ] I also observed a couple of brk() calls, and a small amount of heap growth which may indicate it has a small memory leak, but I am speculating on this. Attached is a full report from a 1 hour of monitoring indicator-power- service for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/indicator-power/+bug/1221871/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
3.8.6-0ubuntu2 + 13.01.0+13.10.20131031-0ubuntu1, can't reproduce heavy CPU load (thanks!) but I do still see some heap growth. I ran gimp, libreoffice, firefox for 296 seconds and observed: heap change: 88 brk() calls, growth of 11496K, or ~38.75K/sec growth CPU usage: 4.38% (3.95% user, 0.43 system) ~11 minor page faults/second So it still seems to be consuming memory quite quickly for me. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: Fix Released Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: Fix Committed 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1234289] Re: accounts-daemon is progressively causing more wakeups over time
Sebastien, is their a way to track the offending client app down? I'd like to get to the root of this issue. -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1234289 Title: accounts-daemon is progressively causing more wakeups over time Status in “accountsservice” package in Ubuntu: New Bug description: Over the past few months accounts-daemon has been increasing the number of wakeup events it generates, see: http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task /accounts-daemon/details/ In April 2013 it was averaging about 13.5 wakeups per minute, now it has increased to 17.5. This isn't much overall, but it does seem like the trend is upwards and every wakeup takes the CPU out of deep sleep and hence consumes a little more power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1234289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I don't see the CPU being pegged and it isn't leaking memory so badly. There is still some memory leakage. I ran health-check (from my PPA, ppa:colin-king/white) against it for over 10 minutes using applications such as LibreOffice, Gimp, Firefox and still observed quite a lot of brks() occurring: Heap Change via brk(): PIDbrk Count Change (K) Rate (K/second) 3222 unity-panel-service 14318612 29.10 (growing moderately fast) so, that's 18Mb in 640 seconds, or about 29K a second. I did reboot my machine before testing and double checked that I was running the package from -proposed. Attached is a report from health-check with the full details. ** Attachment added: leak.log https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199877/+attachment/3897066/+files/leak.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
By the look of things, after all the submenus are rendered the memory consumed by unity-panel-service seems to stabilize, so I am guessing it cache's the menus because after several invocations of the the applications I can't see a great deal more memory being allocated. Is this the intention? If so, how much will it cache over the life time of a session? -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
Installed indicator-appmenu 13.01.0+13.10.20131031-0ubuntu1, rebooted, quick test again, still see: Change in memory (K/second): PID Process TypeSize RSS PSS 3170 unity-panel-service Stack 0.00 0.19 0.19 (growing slowly) 3170 unity-panel-service Heap 98.56237.46237.46 (growing fast) 3170 unity-panel-service Mapped 5.99 4.91 1.95 (growing moderately fast) Heap Change via brk(): PIDbrk Count Change (K) Rate (K/Sec) 3170 unity-panel-service 618292 97.02 (growing moderately fast) Memory Change via mmap() and munmap(): PID mmaps munmaps Change (K) Rate (K/Sec) 3170 unity-panel-service15 15 0 0.00 (no change) -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages, dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Application Menu: Fix Committed Status in Application Menu Indicator 13.10 series: Fix Committed Status in The Ubuntu Power Consumption Project: New Status in Unity: Invalid Status in “gtk+3.0” package in Ubuntu: In Progress Status in “indicator-appmenu” package in Ubuntu: In Progress Status in “unity” package in Ubuntu: Invalid Status in “gtk+3.0” source package in Saucy: Fix Committed Status in “indicator-appmenu” source package in Saucy: In Progress 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/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service memory leak and 100% CPU usage
I ran health-check (ppa:colin-king/white) against unity-panel-service while navigating menus on gimp and thunderbird for 60 seconds and I observed on average over 60 seconds: about 53 minor page faults per second, nearly 1900 context switches a second, over 260 recvfrom() syscalls per second, over 8500 poll() syscalls that timed out with a zero timeout (which means there poll is being abused somewhere), nearly 175K of heap growth per second via brk() nearly 550K of memory growth per second via mmap() Attached is the full log. This is a seriously leaky process with some excessive power consuming polling going on. ** Attachment added: health-check analysis https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1199877/+attachment/3893898/+files/health-check.log -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service memory leak and 100% CPU usage Status in The Ubuntu Power Consumption Project: New Status in Unity: In Progress Status in Unity 7.1 series: In Progress Status in “unity” package in Ubuntu: Triaged Bug description: 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/ubuntu-power-consumption/+bug/1199877/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1238043] [NEW] indicator-datetime-service is opening /etc/localtime every 5 seconds even on a totally idle system
Public bug reported: In an attempt to reduce unnecessary frequent periodic file access to save power, I noticed that indicator-datetime-service is opening and closing /etc/localtime every 5 seconds on my desktop and not apparently reading this file. On the ubuntu phone it is doing the same thing with /etc/writable/localtime. This seems a little excessive, especially because the TZ data doesn't change quite that frequently. It would be useful if this excessive polling on the file could be reduced if possible. ** Affects: indicator-datetime (Ubuntu) Importance: Undecided Status: New ** Tags: mobile-power-consumption ** Tags added: mobile-power-consumption -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-datetime in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1238043 Title: indicator-datetime-service is opening /etc/localtime every 5 seconds even on a totally idle system Status in “indicator-datetime” package in Ubuntu: New Bug description: In an attempt to reduce unnecessary frequent periodic file access to save power, I noticed that indicator-datetime-service is opening and closing /etc/localtime every 5 seconds on my desktop and not apparently reading this file. On the ubuntu phone it is doing the same thing with /etc/writable/localtime. This seems a little excessive, especially because the TZ data doesn't change quite that frequently. It would be useful if this excessive polling on the file could be reduced if possible. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/indicator-datetime/+bug/1238043/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1234289] [NEW] accounts-daemon is progressively causing more wakeups over time
Public bug reported: Over the past few months accounts-daemon has been increasing the number of wakeup events it generates, see: http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task /accounts-daemon/details/ In April 2013 it was averaging about 13.5 wakeups per minute, now it has increased to 17.5. This isn't much overall, but it does seem like the trend is upwards and every wakeup takes the CPU out of deep sleep and hence consumes a little more power. ** Affects: accountsservice (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of DX Packages, which is subscribed to accountsservice in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1234289 Title: accounts-daemon is progressively causing more wakeups over time Status in “accountsservice” package in Ubuntu: New Bug description: Over the past few months accounts-daemon has been increasing the number of wakeup events it generates, see: http://reports.qa.ubuntu.com/power/eventstat/image/2736/machine/1/task /accounts-daemon/details/ In April 2013 it was averaging about 13.5 wakeups per minute, now it has increased to 17.5. This isn't much overall, but it does seem like the trend is upwards and every wakeup takes the CPU out of deep sleep and hence consumes a little more power. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/accountsservice/+bug/1234289/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1199877] Re: unity-panel-service pegs one of my CPUs at 100%
I've traced this and can see ~1MB of brk() heap increase per invocation of gedit. So this is really leaking badly. -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1199877 Title: unity-panel-service pegs one of my CPUs at 100% Status in The Ubuntu Power Consumption Project: New Status in Unity: In Progress Status in “unity” package in Ubuntu: Triaged Bug description: 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/ubuntu-power-consumption/+bug/1199877/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1227710] [NEW] unity-panel-service consumes 100% of my CPU for 8 seconds to while waiting for a global menu to open
Public bug reported: When opening a libreoffice calc menu nothing happens for 8 seconds. Using top one can observe that unity-panel-service is pegging one of my CPUs at 100%. This is 100% repeatable. Just start libreoffice, open the menu. Opening the menu thereafter is often faster. But from a clean start of libreoffice one can always trigger this issue. Attached is a video showing the delay in opening a menu. I'm running in a 2.5 Ghz i5 CPU, so 8 seconds equates to 20 billion clock cycles to open a menu. ** Affects: unity (Ubuntu) Importance: Undecided Status: New ** Attachment added: video of the bug https://bugs.launchpad.net/bugs/1227710/+attachment/3829274/+files/out.ogv -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1227710 Title: unity-panel-service consumes 100% of my CPU for 8 seconds to while waiting for a global menu to open Status in “unity” package in Ubuntu: New Bug description: When opening a libreoffice calc menu nothing happens for 8 seconds. Using top one can observe that unity-panel-service is pegging one of my CPUs at 100%. This is 100% repeatable. Just start libreoffice, open the menu. Opening the menu thereafter is often faster. But from a clean start of libreoffice one can always trigger this issue. Attached is a video showing the delay in opening a menu. I'm running in a 2.5 Ghz i5 CPU, so 8 seconds equates to 20 billion clock cycles to open a menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1227710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1227710] Re: unity-panel-service consumes 100% of my CPU for 8 seconds to while waiting for a global menu to open
Polling system call analysis: unity-panel-service (2776), poll: 2295 immediate timed out calls with zero timeout (non-blocking peeks) 37 repeated timed out polled calls with non-zero timeouts (light polling) 1322 repeated immediate timed out polled calls with zero timeouts (heavy polling peeks) unity-panel-service (2789), poll: 2328 immediate timed out calls with zero timeout (non-blocking peeks) 85 repeated immediate timed out polled calls with zero timeouts (heavy polling peeks) So it appears that some of the polls() are being called with zero timeout and being called many times, which may explain the CPU pegging at 100%. E.g. spinning in a tight loop on poll(). -- You received this bug notification because you are a member of DX Packages, which is subscribed to unity in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1227710 Title: unity-panel-service consumes 100% of my CPU for 8 seconds to while waiting for a global menu to open Status in “unity” package in Ubuntu: New Bug description: When opening a libreoffice calc menu nothing happens for 8 seconds. Using top one can observe that unity-panel-service is pegging one of my CPUs at 100%. This is 100% repeatable. Just start libreoffice, open the menu. Opening the menu thereafter is often faster. But from a clean start of libreoffice one can always trigger this issue. Attached is a video showing the delay in opening a menu. I'm running in a 2.5 Ghz i5 CPU, so 8 seconds equates to 20 billion clock cycles to open a menu. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity/+bug/1227710/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
[Dx-packages] [Bug 1221871] Re: indicator-power-service is a lightly busy all the time
** Tags added: mobile-power-consumption -- You received this bug notification because you are a member of DX Packages, which is subscribed to indicator-power in Ubuntu. https://bugs.launchpad.net/bugs/1221871 Title: indicator-power-service is a lightly busy all the time Status in Touch Preview Images: New Status in “indicator-power” package in Ubuntu: New Bug description: In a vain attempt to reduce power on these phone devices I noticed that indicator-power-service is using just under 1% of one CPU all the time. CPU usage: PID ProcessUSR% SYS% TOTAL% 1358 indicator-power-serv 0.05 0.04 0.08 (very light load) It seems to be waiting on poll() on a couple of threads which cumulatively add up to about 1.68 wakeups a second over a 1 hour analysis: Top polling system calls: PID 1369 indicator-power-serv poll1.3462 polls/sec 1358 indicator-power-serv poll0.3376 polls/sec Total 1.6838 polls/sec This contributes to a bunch of context switching by these threads: Context Switches: PID ProcessVoluntary Involuntary Total Ctxt Sw/Sec Ctxt Sw/Sec Ctxt Sw/Sec 1369 indicator-power-serv10.75 0.1510.90 (moderate) 1358 indicator-power-serv 3.53 0.07 3.60 (low) 1372 indicator-power-serv 0.00 0.00 0.00 (idle) Total 14.29 0.2214.50 [ See the attached log, launchpad formatting sucks ] I also observed a couple of brk() calls, and a small amount of heap growth which may indicate it has a small memory leak, but I am speculating on this. Attached is a full report from a 1 hour of monitoring indicator-power- service for reference. To manage notifications about this bug go to: https://bugs.launchpad.net/touch-preview-images/+bug/1221871/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
