indicator-application-service uses 100% cpu

Bug #672206 reported by Schwarzburg
112
This bug affects 23 people
Affects Status Importance Assigned to Milestone
Application Indicators
Confirmed
Low
Unassigned
indicator-application (Ubuntu)
Confirmed
Low
Unassigned

Bug Description

Since the login, "indicator-application-service" uses 100% cpu.

I have just upgraded from 10.04. I'm using the desktop-interface (but tried unity).
I have a Nvidia card with proprietary drivers.
No idea what other information could be useful.

Revision history for this message
Igor Shalari (elzeon) wrote :

I have observed the same behavior on my netbook where Ubuntu 10.10 is installed.

Revision history for this message
jbraswell (jasonbraswell314) wrote :

I'm seeing it now after upgrading to 10.10 as well.

Revision history for this message
Erez (erez-hadad) wrote :

I concur. Same issue with 10.10, only in my case it's a fresh install of 10.10.
The problematic process is indicator-application-service. After seeing it persist this behavior for about half an hour, I killed it (regular kill) and it restarted automatically but this time it behaves ok.

Revision history for this message
Pythagoras (mayly) wrote :
Download full text (8.9 KiB)

I had this issue right now too. I attached the process using gdb.

Attaching to process 1775
Reading symbols from /usr/lib/indicator-application/indicator-application-service...(no debugging symbols found)...done.
Reading symbols from /usr/lib/libindicator.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libindicator.so.1
Reading symbols from /usr/lib/libgtk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgtk-x11-2.0.so.0
Reading symbols from /usr/lib/libgdk-x11-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk-x11-2.0.so.0
Reading symbols from /usr/lib/libatk-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libatk-1.0.so.0
Reading symbols from /usr/lib/libgio-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgio-2.0.so.0
Reading symbols from /usr/lib/libpangoft2-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangoft2-1.0.so.0
Reading symbols from /usr/lib/libpangocairo-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpangocairo-1.0.so.0
Reading symbols from /usr/lib/libgdk_pixbuf-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgdk_pixbuf-2.0.so.0
Reading symbols from /lib/libm.so.6...(no debugging symbols found)...done.
Loaded symbols for /lib/libm.so.6
Reading symbols from /usr/lib/libcairo.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libcairo.so.2
Reading symbols from /lib/libpng12.so.0...(no debugging symbols found)...done.
Loaded symbols for /lib/libpng12.so.0
Reading symbols from /usr/lib/libpango-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libpango-1.0.so.0
Reading symbols from /usr/lib/libfreetype.so.6...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libfreetype.so.6
Reading symbols from /usr/lib/libfontconfig.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libfontconfig.so.1
Reading symbols from /usr/lib/libgmodule-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgmodule-2.0.so.0
Reading symbols from /usr/lib/libjson-glib-1.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libjson-glib-1.0.so.0
Reading symbols from /usr/lib/libdbusmenu-gtk.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdbusmenu-gtk.so.1
Reading symbols from /usr/lib/libdbusmenu-glib.so.1...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdbusmenu-glib.so.1
Reading symbols from /usr/lib/libdbus-glib-1.so.2...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libdbus-glib-1.so.2
Reading symbols from /lib/libdbus-1.so.3...(no debugging symbols found)...done.
Loaded symbols for /lib/libdbus-1.so.3
Reading symbols from /lib/libpthread.so.0...(no debugging symbols found)...done.
[Thread debugging using libthread_db enabled]
Loaded symbols for /lib/libpthread.so.0
Reading symbols from /usr/lib/libgobject-2.0.so.0...(no debugging symbols found)...done.
Loaded symbols for /usr/lib/libgobject-2.0.so.0
Reading symbols from /usr/l...

Read more...

Revision history for this message
Ted Gould (ted) wrote :

Unfortunately that's not really enough information to debug it. It sounds like indicator-application-service can't connect to DBus, can you use d-feet to see if it's connected?

Changed in indicator-application:
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Morgan Bush (mwbush) wrote :

I also have this problem with 10.10.

Revision history for this message
sslam (e-admin-sheriodessa-info) wrote :

I also have this problem with 10.10

Revision history for this message
sslam (e-admin-sheriodessa-info) wrote :

maybe solution is pkill?

Revision history for this message
Daniel Dunér (daniel-duner) wrote :

I have the same problem on 10.10.

Using d-feet I find:

Bus Name: :1.452
Process: indicator-session-service

Name: :1.452
Unique Name: :1.452
Command Line: /usr/lib/indicator-session/indicator-session-service

Introspection Data:
Objects Paths

Revision history for this message
Rick Sperko (circular-file-launchpad) wrote :

Just saw this bug with a fully updated 10.10

Changed in ubuntu:
status: New → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Application Indicators because there has been no activity for 60 days.]

Changed in indicator-application:
status: Incomplete → Expired
Cristian (cristianrosa)
Changed in indicator-application:
status: Expired → Confirmed
Revision history for this message
Sebastien Bacher (seb128) wrote :

is that still an issue in 11.10?

no longer affects: ubuntu
Changed in indicator-application:
status: Confirmed → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for Application Indicators because there has been no activity for 60 days.]

Changed in indicator-application:
status: Incomplete → Expired
Revision history for this message
Ryan (ryansully) wrote :

Still an issue in 12.10

Changed in indicator-application:
status: Expired → Confirmed
Revision history for this message
Axel G. Rossberg (axel-rossberg) wrote :

In my case (12.10), indicator-application-service uses an entire CPU worth of load only when I go offline. When connecting to the network it quickly comes to senses.

Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug is quite old, whoever is getting the issue should probably open a new ticket with updated infos

Changed in indicator-application:
importance: Low → High
importance: High → Low
Revision history for this message
B Bobo (yout-bobo123) wrote :

If users are still experiencing the same issue with indicator-application-service, why should they open a new ticket? That would just divide the useful information into two different places, wouldn't it?

Revision history for this message
Eugene Kirpichov (ekirpichov) wrote :
Download full text (4.2 KiB)

I observed this behavior while I had an unread message notification in Psi messenger. indicator-application was using 100% cpu (according to "top"), but it immediately stopped doing so as soon as I read the notification.

This happened at least two times; then I decided to debug things.

The top entry looks like this:
  PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
  745 kirpicho 20 0 538m 136m 3888 R 99.8 0.4 3603:49 indicator-appli

Here's some strace data while it's consuming 100% CPU:
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 1 ([{fd=3, revents=POLLIN}])
read(3, "\3\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f764400c1c0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f764400bd50, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x12af0b0, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f764400c1c0, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f764400c1c0, FUTEX_WAKE_PRIVATE, 1) = 1
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f764400c1c0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f764400bd50, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x12af0b0, FUTEX_WAKE_PRIVATE, 1) = 1
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 1 ([{fd=3, revents=POLLIN}])
read(3, "\3\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f76516c1720, FUTEX_WAKE_PRIVATE, 1) = 0
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x12af0b0, FUTEX_WAKE_PRIVATE, 1) = 1
futex(0x7f76440024a0, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN (Resource temporarily unavailable)
futex(0x7f76440024a0, FUTEX_WAKE_PRIVATE, 1) = 0
poll([{fd=3, events=POLLIN}, {fd=7, events=POLLIN}], 2, 0) = 1 ([{fd=3, revents=POLLIN}])
read(3, "\1\0\0\0\0\0\0\0", 16) = 8
write(5, "\1\0\0\0\0\0\0\0", 8) = 8
futex(0x7f764400c1c0, FUTEX_WAKE_PRIVATE, 1) = 1

A stack trace from gdb looks like this:
(gdb) bt
#0 0x00007f7651929f20 in g_list_length () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1 0x00000000004035e4 in ?? ()
#2 0x000000000040464e in ?? ()
#3 0x00007f7651e960c7 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#4 0x00007f7651eee56d in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#5 0x00007f7651e960c7 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#6 0x00007f7651ee494a in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#7 0x00007f7651e960c7 in g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#8 0x00007f7651e961c9 in ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
#9 0x00007f765192cd13 in g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#10 0x00007f765192d060 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#11 0x00007f765192d45a in g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#12 0x0000000000402e59 in ?? ()
#13 0x00007f765132976d in __libc_start_main (main=0x402de0, argc=1, ubp_a...

Read more...

Revision history for this message
Michał Wróbel (maw) wrote :

Eugene, which version of Ubuntu do you have? I remember I had this bug back circa 2012 (11.10? 12.04?). I don't remember having it on 13.04 anymore.

Revision history for this message
hamish (hamish-b) wrote :

seeing this currently on 12.04 from multiple (screen locked) user accounts on a multi-user workstation.

killall'd, but hud-service and unity-panel-service are still humming away at 1-2% CPU.

Ted Gould (ted)
Changed in indicator-application (Ubuntu):
importance: Undecided → Low
status: New → Confirmed
Revision history for this message
Felix Moreno (info-justdust) wrote :

Hi its happening to me in ubuntu 16.10 when usin retroshare software.

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.