Crash When Using Phone

[Rick Spencer]

I tried to use unity, but it seemed frozen. I adb shelled in, and top showed apport running at 100%. This crash file was there.

It occurred to me what I was doing around when it crashed. I had just updated over the air. I ran some apps, like the messaging app, and the contacts from the launcher, they worked fine. Then I tried launching other apps, like the music app. They did not launch, but rather resulted in a black screen. These were apps that I had previously "locked to launcher"ed.

[Alexander Sack (asac)]

20:44 < rickspencer3> ogra_, asac so ... my unity crash, while I was out I remembered what I was doing
20:45 < rickspencer3> is it possible that launching updates that I had previously "locked to launcher" could have led to the issue?
20:45 < ogra_> the click update manager you mean ?
20:45 < ogra_> shouldnt cause such crashers
20:46 < ogra_> (theoretically)
20:46 < rickspencer3> ogra_, I just ran all the updates in the updater, I thought it was just Ubuntu that go updated
20:46 < rickspencer3> ogra_, well, the launcher items for sure didn't launch the app
20:46 < asac> rickspencer3: do those launchers work now?
20:46 < rickspencer3> asac, well, sadly it only occurred to me later that that could have been the reproducer
20:47 < rickspencer3> so I took off the launcher items, ran the apps from the scope, and repinned to the launcher
20:47 < rickspencer3> they work now
20:47 < rickspencer3> so, basically, the answer is "yes I think I destroyed the state necessary to reproduce the crasher"
20:47 < rickspencer3> :/

[kevin gunn (kgunn72)]

do we know the original image # ?

[Robert Bruce Park (robru)]

I've been playing with this, here is what I saw:

1. flashed image 250.

2. Started locking icons to launcher (run the app, open launcher, long-press the icon, choose lock to launcher).

3. locked camera, gallery, music, file manager.

4. shortly after this unity became unresponsive. ssh'ing in and running `top` showed apport taking 97% CPU for an extended period of time. When it completed, I noticed that unity had restarted, but the new unity instance was also unresponsive (stuck on welcome screen). Then, running top showed "qmlscene" taking 108% CPU (no indication of which qmlscene it was. Running `ps aux|grep qml` showed music app taking 50% CPU. Note that this was recently bootstrapped and did not have any music files in place.

Restarted the device, seems to be fine now.

[Robert Bruce Park (robru)]

Asac suggested I try closing apps after locking them, and indeed using that approach I was able to lock many apps without hitting any issue. So this suggests either an OOM issue or perhaps unity just becomes crash-prone when 4+ apps are running.

[Robert Bruce Park (robru)]

Apps that were locked to launcher in image 250 launch inconsistently in image 295.

apps that launched normally include: friends, clock, browser, file manager,

apps that did not launch (no black screen as rick describes, but simply no response whatsoever to tapping the launcher): facebook, music

apps that launch to an unresponsive black screen (and don't appear in running apps list after launching): gallery, camera

[Michał Sawicz (saviq)]

Please make sure to apport-cli the .crash files on devices (or run /usr/share/apport/whoopsie-upload-all, which will process them and upload to errors.ubuntu.com), otherwise they lack vital information (like which package version crashed).

I'm unable to get anything from the above .crash files, will be trying to reproduce locally.

[Alexander Sack (asac)]

on the package versions: rick is using the currently promoted devel image; you should be able to extract the package versions from the .manifest.

[kevin gunn (kgunn72)]

hmm, potentially related ?
https://bugs.launchpad.net/ubuntu/+source/unity8/+bug/1339883

[Michał Sawicz (saviq)]

Not really, static CPU usage in the 10% range is probably something that is happening when it shouldn't, 100% CPU is just something looped.

Has anyone seen this recently in any case?

[Launchpad Janitor (janitor)]

[Expired for unity8 (Ubuntu) because there has been no activity for 60 days.]