Closed
Bug 1268335
Opened 8 years ago
Closed 7 years ago
Getting screen size in content process costs an additional sync IPC
Categories
(Core :: DOM: Core & HTML, defect)
Core
DOM: Core & HTML
Tracking
()
RESOLVED
DUPLICATE
of bug 1194751
People
(Reporter: xidorn, Unassigned)
References
(Blocks 2 open bugs)
Details
(Whiteboard: btpp-fixlater)
For avoid potential additional resize reflow, we change the window dimensions to the screen dimensions in advance for fullscreen change in the content process. Currently, we get the size of the screen in the content process, which costs an additional IPC call, which could be avoided if we pass the screen together with the fullscreen change message itself. It isn't too expensive, but it's still worth several tens of ms we may want to avoid.
Reporter | ||
Comment 1•8 years ago
|
||
It's worth 10% of the time.
Comment 2•8 years ago
|
||
tens of ms? huh, parent process must be busy doing something else if it is that slow to reply.
Reporter | ||
Comment 3•8 years ago
|
||
The parent process could be reflowing the UI.
(In reply to Olli Pettay [:smaug] from comment #2) > tens of ms? huh, parent process must be busy doing something else if it is > that slow to reply. We often have several CPU cores decoding video while transitioning to full screen.
Comment 5•8 years ago
|
||
I'm guessing this is something we/Xidorn aim to fix in the next few months => "fixlater".
Whiteboard: btpp-fixlater
Updated•7 years ago
|
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → DUPLICATE
Assignee | ||
Updated•5 years ago
|
Component: DOM → DOM: Core & HTML
You need to log in
before you can comment on or make changes to this bug.
Description
•