Closed Bug 1299069 Opened 8 years ago Closed 8 years ago

[e10s] Significant graphics performance degradation when moving mouse in a circular motion on top of the content area for a while.

Categories

(Core :: General, defect, P3)

Product:
Core
Component:
General
Version:
46 Branch
Platform:
x86
Windows 10
Type:
defect

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla52
Tracking Flags:
Tracking Status
e10s + ---
firefox48 --- wontfix
firefox49 --- wontfix
firefox-esr45 --- unaffected
firefox50 --- wontfix
firefox51 --- fixed
firefox52 --- fixed

People

(Reporter: alice0775, Assigned: kats)

References

(Blocks 1 open bug)

Details

(Keywords: multiprocess, perf, regression, Whiteboard: [gfx-noted])

Build Identifier: https://hg.mozilla.org/mozilla-central/rev/1a5b53a831e5a6c20de1b081c774feb3ff76756c Mozilla/5.0 (Windows NT 10.0; WOW64; rv:51.0) Gecko/20100101 Firefox/51.0 ID:20160829030202 With e10s, it becomes 40% slow. Without e10s, the performance degradation does not occur almost Reproducible: always Steps To reproduce: 1. Open http://www.vsynctester.com/ 2. Moving mouse in a circular motion on top of the content area for a while. Actual Results: becomes 75fps -> 40fps Expected Results: Reduction should be small.
Whiteboard: [DUPEME]
Blocks: e10s
Sounds like a buildup of cursor events we forward. I'm not seeing it on this site so I'd bet it shows up on slow hardware.
Blocks: e10s-perf
No longer blocks: e10s, 1222662
tracking-e10s: ? → +
Flags: needinfo?(jmathies)
Priority: -- → P3
Version: 51 Branch → 46 Branch
Whiteboard: [DUPEME] → [DUPEME][gfx-noted]
This is not really a graphics bug, moving to Core::General which is where bug 1222662 lived.
Component: Graphics → General
Keywords: multiprocess
Can we get some telemetry on mouse event forwarding latency so we can decide how serious it is?
Flags: needinfo?(jmathies)
Or wait, did you mean in our event queue or in some sort of OS event queue? (/me doesn't know how this stuff works in case it wasn't clear) If the former, maybe bug 1303296 could help?
I can reproduce the problem on 50.0. However, I can no longer reproduce the problem on Nightly53.0a1 and 51.0b2. Fixed range: https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=9e9080a2e3462fc576b679603853f4395fadff8f&tochange=75abc730f8202005d6469a7ec324b7aba5a89374 Fixed by: 75abc730f820 Kartikaya Gupta — Bug 1300421 - Back out 4 csets from bug 1288760 for regressing event coordinate reporting. r=jfkthame
status-firefox51: affected → ---
Depends on: 1300421
Assignee: nobody → bugmail
Status: NEW → RESOLVED
Closed: 8 years ago
status-firefox51: ? → fixed
status-firefox52: ? → fixed
Flags: needinfo?(jmathies)
Resolution: --- → FIXED
Whiteboard: [DUPEME][gfx-noted] → [gfx-noted]
Target Milestone: --- → mozilla52
You need to log in before you can comment on or make changes to this bug.