[Bug 1211417] Re: whoopsie takes 100% CPU on the phone

[Evan Dandrea]

[18:06:03] <ev>	 desrt: would you be able to judge whether the problem lies in glib or in whoopsie from that stack trace?
[18:06:46] <ev>	 (the final one, that is - it's got the clearest listing)
[18:07:04] <desrt>	 this stack trace is ... not legit
[18:07:15] <desrt>	 #4  g_main_context_dispatch (context=0x40531cd5 <g_pattern_spec_free+8>) at /build/buildd/glib2.0-2.37.5/./glib/gmain.c:3641 No locals. #5  0x4054132a in g_test_build_filename_va (file_type=<optimized out>, first_path=<optimized out>, ap=...) at /build/buildd/glib2.0-2.37.5/./glib/gtestutils.c:2938
[18:07:20] <desrt>	 this is not possible....
[18:07:43] <desrt>	 neither of those functions call each other
[18:07:47] <desrt>	 even indirectly
[18:07:55] <ev>	 https://launchpadlibrarian.net/147473611/whoopsie2.crash
[18:08:52] <ev>	 but yeah, perhaps we've corrupted the stack inside whoopsie as gdb hints at
[18:09:22] <desrt>	 i'd whip out valgrind as a first step...
[18:09:40] <ev>	 yeah
[18:09:44] <ev>	 will do in the morn'

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1211417

Title:
  whoopsie takes 100% CPU on the phone

Status in Touch Preview Images:
  Confirmed
Status in Ubuntu error tracker client (whoopsie):
  Confirmed
Status in “glib2.0” package in Ubuntu:
  Confirmed
Status in “whoopsie” package in Ubuntu:
  Confirmed

Bug description:
  device: mako
  Whoopsie 0.2.20

  I just noted whoopise taking 100% cpu on two of the devices in the
  lab, its quite critical since it may kill our phones.

To manage notifications about this bug go to:
https://bugs.launchpad.net/touch-preview-images/+bug/1211417/+subscriptions