ubuntu-sdk-bugs team mailing list archive

[Michał Sawicz <michal.sawicz@xxxxxxxxxxxxx>]

** Project changed: qtmir => qtmir (Ubuntu)

-- 
You received this bug notification because you are a member of Ubuntu
SDK bug tracking, which is subscribed to qtdeclarative-opensource-src in
Ubuntu.
https://bugs.launchpad.net/bugs/1588929

Title:
  cursor interactions cause lockup with pocket desktop

Status in Mir:
  Invalid
Status in qtdeclarative-opensource-src package in Ubuntu:
  New
Status in qtmir package in Ubuntu:
  Invalid
Status in unity8 package in Ubuntu:
  Fix Released

Bug description:
  To reproduce (seen on frieza):

  Connect a mouse to a pocket desktop setup.
  Launch a 'legacy' application, like gedit, in windowed mode. The problem is not seen with 'native' applications, it seems that the setting the custom cursor bitmap that Xmir does is the precipitating event for the problem.
  Rapidly move the cursor over the edge of the window to force rapid cursor transitions.
  After a while (usually between 30s-2 minutes of the rapid movement), the desktop will lock up.

  First noted on mir 0.23 testing (silo 69), but also seen with 0.22.1.

  USC is still alive, and doesn't look locked up. Unity8 is locked.

  Render logs from Qt for the last 2 frames (including the one that's locked)
  http://pastebin.ubuntu.com/16953202/

  BT of threads when attaching to unity8 when stuck:
  http://pastebin.ubuntu.com/16952340/
  note: it seems that thread 1 is the render loop, and thread 2 is the render thread. Thread 2 doesn't quite seem stuck (seems to be busy, and doesnt unblock), and thread 1 is stuck waiting for a response from thread 2

  If I disable the notification of the cursor change callback in mir (just commenting out here)
  http://bazaar.launchpad.net/~mir-team/mir/0.22/view/head:/src/server/scene/basic_surface.cpp#L693
  This breaks the cursor updating for Xmir apps, but averts the crash

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