touch-packages team mailing list archive

[Thomas Voß <1380848@xxxxxxxxxxxxxxxxxx>]

I will try to come up with a distilled down test case illustrating that
libdbus-cpp is not the cause but a symptom of the issue. Point being
that it certainly shows up in the stack traces, but it sits waiting in
all of them (specifically for the system settings crash).

-- 
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:
  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