Deadlock in Unity8
Bug #1421308 reported by
Cemil Azizoglu
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
QtMir |
Invalid
|
Critical
|
Unassigned | ||
qtmir (Ubuntu) |
Invalid
|
Critical
|
Unassigned | ||
unity8 (Ubuntu) |
New
|
Critical
|
Unassigned |
Bug Description
Got a lockup on boot, here's a another gdb "t a a bt".
Changed in unity8 (Ubuntu): | |
importance: | Undecided → Critical |
summary: |
- Yet another Mir deadlock + Deadlock in Unity8 |
tags: | added: vivid |
tags: | added: vivid-stab-candidate |
To post a comment you must log in.
This doesn't seem related to mir code - it looks more like a flaw with Qt DBus/QMutex .
From the gdb dump, Thread 11 is waiting on a Qt signal to be dispatched (BlockedQueuedC onnection) , so an event is posted to the main thread (Thread #1) which should signal the semaphore given.
Thread 1 seems to be responding to a DBus event waiting on a mutex lock through syscall(__NR_futex, FUTEX_WAIT,....)
It's not apparent from the gdb dump why Thread #1 is stuck there.