touch-packages team mailing list archive

Thread
Date

[Bug 1421308] Re: Deadlock in Unity8

To: touch-packages@xxxxxxxxxxxxxxxxxxx
From: Alberto Aguirre <alberto.aguirre@xxxxxxxxxxxxx>
Date: Tue, 17 Feb 2015 19:40:35 -0000
Reply-to: Bug 1421308 <1421308@xxxxxxxxxxxxxxxxxx>
Sender: bounces@xxxxxxxxxxxxx

Right Thread #1 would be the one that would unblock Thread #11;  it's
not clear why Thread #1 is stuck waiting for that futex to signal.

An inspection of the code involved does NOT reveal possible mutex
locking order issues (as far as I can see). Perhaps more inspection
around that DBUs debug dispatch mutex would reveal the issue.

-- 
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/1421308

Title:
  Deadlock in Unity8

Status in Qt integration with the Mir display server:
  Invalid
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  New

Bug description:
  Got a lockup on boot, here's a another gdb "t a a bt".

To manage notifications about this bug go to:
https://bugs.launchpad.net/qtmir/+bug/1421308/+subscriptions