Comment 11 for bug 1398436

Steps to reproduce

0) make sure that USB is unplugged
1) launch camera
2) lock phone and wait 5 seconds
3) resume phone and wait 5 seconds
4) unlock phone

Expected result:
Depending on how fast the phone was unlocked the camera is either fully functional with the camera viewfinder showing the camera video feed or a black screen is shown for a split second before the camera becomes functional.

Current result:
The camera app is not rerendered for a few seconds.
The process is not suspended anylonger as expected but:
 a) Qt.application.active is not set to true for a few seconds
 b) no rendering occurs for that period of time
 c) inputs are not taken into account for that period of time (but they are reliably delivered once the application unfreezes)

Important notes:
- This happens on krillin with both RTM and vivid
- This does not happen on mako
- It happens with a freshly flashed phone and once reproduced tends to happen more often
- It happens with a just rebooted phone with no other app (other than Unity8) running
- When it happens the greeter screen's background usually is black for a split second upon resuming the phone
- It happens even with MIR_SERVER_DISABLE_OVERLAYS=true
- No piece of code in the stack seems to be setting eglSwapInterval(0) (it is one by default for all apps)
- It was not possible to reproduce it so far with other apps
- The stack traces of the app in the normal case and the broken case seem identical (Normal bt: http://pastebin.ubuntu.com/9474590/ & Frozen bt: http://pastebin.ubuntu.com/9474521/ ) suggesting that the camera process itself is behaving normally