Very interestingly the crash is deep down in the qml engine where we are accessing a property index of an object and said property index doesn't exist.
This crash is has a very similar backtrace to crashes we had when the QML cache was stale, the problem here is that clearing the cache still makes it crash for future runs, so it's not because the cache is stale. More interestingly if i disable the QML cache (you can do that by prepending # to all the lines of /etc/profile.d/qml_qv4_jit_cache.sh ) i can run the loop above over 70 times without it crashing. So maybe it's that our code for the QML cache has a bug? -- 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/1473471 Title: unity8 crashes on boot Status in Canonical System Image: New Status in unity8 package in Ubuntu: Confirmed Bug description: On rc-proposed/bq-aquaris.en/krillin #64 and rc- proposed/meizu.en/arale #56 unity8 often crashes on boot, introducing a long delay while apport is doing its work. The process respawns and there doesn't seem to be any impact after boot. Report on errors.u.c: https://errors.ubuntu.com/oops/34eea84c-270c- 11e5-a0a8-fa163e5bb1a2 Most of the time maliit-server also crashes. I reported bug 1473469 How to reproduce the crash: * Make sure your /var/crash in the phone is empty * run in the phone while [ true ]; do echo "Checking if there is crash files"; output=`adb shell ls /var/crash`; if [ "x$output" != "x" ]; then break; fi; echo "No crash files, Rebooting"; adb reboot; echo "Sleeping for 100 seconds"; echo ""; sleep 100; done Will stop because crash files have been generated in about 5 iterations To manage notifications about this bug go to: https://bugs.launchpad.net/canonical-devices-system-image/+bug/1473471/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
