[regression] Mir server uses too much CPU during touch scrolling
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Mir |
Fix Released
|
High
|
Daniel van Vugt | ||
0.7 |
Invalid
|
Undecided
|
Unassigned | ||
mir (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
mir (Ubuntu RTM) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[regression] Mir server uses too much CPU during touch events.
Until recently constant touch events never cause the CPU usage of my Mir server to exceed 50%. However with the latest code it's 80-90% CPU.
I'm fairly sure this is caused by my recent change:
-------
revno: 1936 [merge]
author: Daniel van Vugt <email address hidden>
committer: Tarmac
branch nick: development-branch
timestamp: Thu 2014-09-25 06:06:57 +0000
message:
Fix jerky/stuttering event delivery that could happen inside
nested servers sometimes (LP: #1372300)
Waiting significantly longer than a frame before consuming previously
batched events is too dangerous in slow raw-event environments
(nested servers or very slow input devices). It causes frame skipping.
. Fixes: https:/
Approved by Alexandros Frantzis.
-------
Related branches
- Kevin DuBois (community): Approve
- PS Jenkins bot (community): Approve (continuous-integration)
- Alexandros Frantzis (community): Approve
-
Diff: 41 lines (+13/-2)2 files modifiedsrc/common/input/android/android_input_receiver.cpp (+9/-1)
tests/unit-tests/client/input/test_android_input_receiver.cpp (+4/-1)
Changed in mir: | |
status: | Fix Committed → Fix Released |
Changed in mir (Ubuntu): | |
status: | Fix Released → Invalid |
This bug is invalid for 0.7 right now. Only exists in 0.8. Let's keep it that way.