The spinning futex wait we get in the strace:
2391 futex(0x1072a70, FUTEX_WAIT_PRIVATE, 2, NULL) = -1 EAGAIN
(Resource temporarily unavailable)
Comes from:
25 Thread 0xb528f3e0 (LWP 2391) "Binder_1" __libc_do_syscall ()
at ../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#0 __libc_do_syscall () at
../ports/sysdeps/unix/sysv/linux/arm/libc-do-syscall.S:44
#1 0xb6a951e4 in __lll_lock_wait (futex=0xfffffff5, futex@entry=0x1072a70,
private=<optimized out>)
at ../ports/sysdeps/unix/sysv/linux/arm/nptl/lowlevellock.c:46
#2 0xb6a91840 in __GI___pthread_mutex_lock (mutex=0x1072a70) at
pthread_mutex_lock.c:79
#3 0x000de3a8 in std::mutex::lock() ()
#4 0x0011f064 in ?? ()
#5 0x000e390c in core::Signal<void>::operator()() ()
#6 0x000e390c in core::Signal<void>::operator()() ()
#7 0xb676115e in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to dbus-cpp in Ubuntu.
https://bugs.launchpad.net/bugs/1380848
Title:
[TOPBLOCKER] Apps and services use large amount of CPU after unity8
resets
Status in Media Hub:
Triaged
Status in “dbus-cpp” package in Ubuntu:
New
Bug description:
I noticed that media-hub-service can get into a state where it uses a
large amount of CPU.
Steps to reproduce
1) Start music-app
2) Play music
3) Pause music
4) Close the music-app
5) $ pkill unity8 (to emulate unity crashing a resetting)
Notice that media-hub-service is now using a large amount of CPU, note
this [0] is the media-hub.log at the time.
The device has to be reset to get the CPU usage back to normal.
0 - http://pastebin.ubuntu.com/8553411/
To manage notifications about this bug go to:
https://bugs.launchpad.net/media-hub/+bug/1380848/+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
