Closed
Bug 1227604
Opened 9 years ago
Closed 9 years ago
Compositor events can be in the wrong order
Categories
(Core Graveyard :: Widget: Android, defect)
Tracking
(firefox44 fixed, firefox45 fixed, b2g-v2.5 fixed)
RESOLVED
FIXED
mozilla45
People
(Reporter: jchen, Assigned: jchen)
Details
Attachments
(1 file)
1.22 KB,
patch
|
snorp
:
review+
ritu
:
approval-mozilla-aurora+
|
Details | Diff | Splinter Review |
I found a bug in nsAppShell::LegacyGeckoEvent::PostTo, where a compositor event can be inadvertently added to the front of the event queue, when there are existing compositor events already in the queue.
Assignee | ||
Comment 1•9 years ago
|
||
When the queue only contains compositor events, a compositor event should go to the back of the queue to maintain order.
Attachment #8691448 -
Flags: review?(snorp)
Comment on attachment 8691448 [details] [diff] [review] Fix compositor event order (v1) Review of attachment 8691448 [details] [diff] [review]: ----------------------------------------------------------------- This seems to put it at the back of the queue in the case where we have no other compositor events, which does not match your comment. Is that what you intended? Seems wrong to me...
Attachment #8691448 -
Flags: review?(snorp) → review-
Assignee | ||
Comment 3•9 years ago
|
||
(In reply to James Willcox (:snorp) (jwillcox@mozilla.com) from comment #2) > Comment on attachment 8691448 [details] [diff] [review] > Fix compositor event order (v1) > > Review of attachment 8691448 [details] [diff] [review]: > ----------------------------------------------------------------- > > This seems to put it at the back of the queue in the case where we have no > other compositor events, which does not match your comment. Is that what you > intended? Seems wrong to me... It's kind of confusing, but |event| is null when the queue only has compositor events. In that case, we want the new event to go to the back of the queue to maintain order. If the queue only has non-compositor events, |event| will point to the first element in the queue, and we correctly insert the new event in front of it.
Assignee | ||
Updated•9 years ago
|
Attachment #8691448 -
Flags: review- → review?(snorp)
Attachment #8691448 -
Flags: review?(snorp) → review+
Assignee | ||
Comment 4•9 years ago
|
||
Try: https://treeherder.mozilla.org/#/jobs?repo=try&revision=473a369fecbf&selectedJob=14106296
Keywords: checkin-needed
Comment 6•9 years ago
|
||
bugherder landing |
https://hg.mozilla.org/integration/mozilla-inbound/rev/3b624179e13b
Assignee | ||
Comment 7•9 years ago
|
||
Comment on attachment 8691448 [details] [diff] [review] Fix compositor event order (v1) Approval Request Comment [Feature/regressing bug #]: Bug 1197976 [User impact if declined]: Possible glitches when showing or hiding the app. [Describe test coverage new/current, TreeHerder]: Locally [Risks and why]: Very small; patch corrects a single-line mistake and doesn't affect anything else. [String/UUID change made/needed]: None
Attachment #8691448 -
Flags: approval-mozilla-aurora?
Comment 8•9 years ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/3b624179e13b
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox45:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla45
Comment on attachment 8691448 [details] [diff] [review] Fix compositor event order (v1) Aurora44+
Attachment #8691448 -
Flags: approval-mozilla-aurora? → approval-mozilla-aurora+
status-firefox44:
--- → affected
Comment 10•9 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-aurora/rev/a0e9399f1eef
Comment 11•9 years ago
|
||
bugherder uplift |
https://hg.mozilla.org/releases/mozilla-b2g44_v2_5/rev/a0e9399f1eef
status-b2g-v2.5:
--- → fixed
Updated•3 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•