Yeah it's a deadlock in mir, specifically between the compositor Thread
and the main loop:
The TimeoutFrameDroppingPolicy has timedout, so it owns the internal
alarm mutex and attemps to drop a frame, so it waits for the BufferQueue
mutex.
The compositor thread is releasing a buffer, so it calls
BufferQeueue::compositor_release, which owns the BufferQueue mutex and
attempts to update the TimeoutFrameDroppingPolicy (since a buffer is
being freed) but it waits to own the internal alarm mutex so deadlock.
** Also affects: mir
Importance: Undecided
Status: New
** Changed in: mir
Importance: Undecided => High
** Changed in: mir
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1339700
Title:
Device locks randomly on welcome screen
To manage notifications about this bug go to:
https://bugs.launchpad.net/mir/+bug/1339700/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
