touch-packages team mailing list archive

[Bill Filler <1387959@xxxxxxxxxxxxxxxxxx>]

I just rebooted the phone and attached to unity8 with gdb:
- sudo gdb --pid XXXX /usr/bin/unity8

First strange thing noticed, after typing continue in gdb, I see Threads endlessly being created and destroyed, this never stops:
[New Thread 0xa18d2450 (LWP 11331)]
[Thread 0xa18d2450 (LWP 11331) exited]
repeated continously..

Then I use the phone, call it a few times. Finally it crashes. Gdb shows me:
Program received signal SIGSEGV, Segmentation fault.
0xb61d342a in _int_malloc (av=av@entry=0xb62694e8 <main_arena>, bytes=bytes@entry=8)
    at malloc.c:3351
3351	malloc.c: No such file or directory.
(gdb) 
Continuing.
[Thread 0x9a905450 (LWP 11767) exited]
[Thread 0xa18d2450 (LWP 11434) exited]
[Thread 0xb37e0450 (LWP 2488) exited]
[Thread 0xb2fe0450 (LWP 2489) exited]
[Thread 0xb2729450 (LWP 2494) exited]
[Thread 0xb1c02450 (LWP 2497) exited]
[Thread 0xb12feb40 (LWP 2498) exited]
[Thread 0xb12f8450 (LWP 2499) exited]
[Thread 0xb0af8450 (LWP 2500) exited]
[Thread 0xb00b2450 (LWP 2501) exited]
[Thread 0xaf6ff450 (LWP 2502) exited]
[Thread 0xaecff450 (LWP 2503) exited]
[Thread 0xae4ff450 (LWP 2504) exited]
[Thread 0xac522450 (LWP 2540) exited]
[Thread 0xabd22450 (LWP 2547) exited]
[Thread 0xaaa5f450 (LWP 2621) exited]
[Thread 0xa93ec450 (LWP 2674) exited]
[Thread 0xa8425450 (LWP 2788) exited]
[Thread 0xa761c450 (LWP 2797) exited]
[Thread 0xa5e62450 (LWP 2805) exited]
[Thread 0xa46fc450 (LWP 2831) exited]
[Thread 0xa3e92450 (LWP 2832) exited]
[Thread 0xa3692450 (LWP 2833) exited]
[Thread 0xa2e91450 (LWP 2874) exited]
[Thread 0xa10d2450 (LWP 2907) exited]
[Thread 0xa08d2450 (LWP 2908) exited]
[Thread 0xa00d2450 (LWP 2909) exited]
[Thread 0x9f285450 (LWP 3037) exited]
[Thread 0x9c105450 (LWP 3039) exited]
[Thread 0x9b905450 (LWP 3040) exited]
[Thread 0x9b105450 (LWP 3041) exited]
[Thread 0xb6fc8000 (LWP 2454) exited]

Program terminated with signal SIGSEGV, Segmentation fault.
The program no longer exists.
(gdb) break
Breakpoint 1 at 0xb61d342a: file malloc.c, line 3351.

So I believe we are running out of memory because of all these threads
being created. I do not know how to determine who is creating the
threads or why, but assuming this is the issue. Saw the exact same thing
when attaching to system-settings after unity8 crashed.

-- 
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to unity8 in Ubuntu.
https://bugs.launchpad.net/bugs/1387959

Title:
  unity8 crash in image krillin rtm 139

Status in “unity8” package in Ubuntu:
  New

Bug description:
  Earlier today, a few QA folks tested image krillin rtm 138 plus silo
  13, and found that it fixed the unity8 crash from bug 1382595.

  Silo 13 plus silo 10 landed in image 139.

  Now, in image 139, unity8 is crashy again.  Olli mentioned getting two
  crashes within a few minutes, and I got a unity8 crash while trying to
  accept an incoming call.  I'm not sure if it's the same crash as
  before, or if it's a new one.

  Attached is the crash dump I got just after hitting 'accept' for an
  incoming call.  I tried to pre-process it in apport-cli, but it failed
  with "Sorry, the program "unity8" closed unexpectedly  //  Your
  computer does not have enough free memory to automatically analyze the
  problem and send a report to the developers."

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1387959/+subscriptions