unity8 crashed with SIGSEGV in mir::frontend::ClientBufferTracker::client_has()

Bug #1339610 reported by Michał Sawicz
14
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mir
Invalid
Critical
Unassigned
mir (Ubuntu)
Invalid
Undecided
Unassigned
unity8 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

This happened during UITK autopilot tests in smoketesting of image #121:

http://ci.ubuntu.com/smokeng/utopic/touch/mako/121:20140709:20140709/8946/ubuntuuitoolkit/

ProblemType: Crash
DistroRelease: Ubuntu 14.10
Package: unity8 7.90+14.10.20140707-0ubuntu1
Uname: Linux 3.4.0-5-mako armv7l
ApportVersion: 2.14.4-0ubuntu1
Architecture: armhf
CurrentDesktop: Unity
Date: Wed Jul 9 05:45:03 2014
ExecutablePath: /usr/bin/unity8
ExecutableTimestamp: 1404736464
InstallationDate: Installed on 2014-07-09 (0 days ago)
InstallationMedia: Ubuntu Utopic Unicorn (development branch) - armhf (20140709-020204)
ProcCmdline: unity8
ProcCwd: /home/phablet
Signal: 11
SourcePackage: unity8
StacktraceTop:
 mir::frontend::ClientBufferTracker::client_has(mir::graphics::BufferID const&) const () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22
 ?? () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22
 mir::compositor::BufferQueue::give_buffer_to_client(mir::graphics::Buffer*, std::unique_lock<std::mutex>) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22
 mir::compositor::BufferQueue::release(mir::graphics::Buffer*, std::unique_lock<std::mutex>) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22
 mir::compositor::BufferQueue::compositor_release(std::shared_ptr<mir::graphics::Buffer> const&) () from /usr/lib/arm-linux-gnueabihf/libmirserver.so.22
Title: unity8 crashed with SIGSEGV in mir::frontend::ClientBufferTracker::client_has()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm autopilot cdrom dialout dip nopasswdlogin plugdev sudo tty video

Revision history for this message
Michał Sawicz (saviq) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

Stacktrace: No stack.
StacktraceSource:

StacktraceTop:

ThreadStacktrace:

Changed in mir (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

no debug symbol package found for qtdeclarative5-ubuntu-thumbnailer0.1
no debug symbol package found for libbz2-1.0
no debug symbol package found for libautopilot-qt
no debug symbol package found for libmirclientplatform-android
no debug symbol package found for qtdeclarative5-gsettings1.0
no debug symbol package found for liburcu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-armhf-retrace
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Incomplete. The retracing service can only decipher crashes from pure Ubuntu installations where all packages have known debug symbols available. So no PPAs or bespoke packages.

information type: Private → Public
Changed in mir:
status: New → Incomplete
Revision history for this message
Michał Sawicz (saviq) wrote :

Well, this was a pure Ubuntu installation... The smoke tests run on devices which are just flashed with the current devel-proposed image. Not sure why the retracer would not like the .crash file... Maybe debug packages weren't available in ddebs yet...

I'm currently trying to reproduce locally.

Revision history for this message
Oliver Grawert (ogra) wrote :

this is a pure ubuntu installation running the tests in the labs ... it indeed might be that the installation of the tests taint the virgin installation ...

Revision history for this message
Martin Pitt (pitti) wrote :

Argh, for some reason gdb-multiarch disappeared from teh retracter schroots. I put it back now, so hopefully from now on we should get some more sensible results.

tags: added: lt-category-noimpact lt-date-20140708 lt-prio-low
Changed in mir:
importance: Undecided → Critical
tags: added: lt-whitelisted
Revision history for this message
kevin gunn (kgunn72) wrote :

so considering uitk ap tests are running each day and no one has uploaded more info.
And i just ran uitk back to back 10 times without crashing.
I'm marking this as invalid.
please reopen if its witnessed.

Changed in mir:
status: Incomplete → Invalid
Changed in unity8 (Ubuntu):
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.