Closed
Bug 1612961
Opened 5 years ago
Closed 5 years ago
Disable the socket process
Categories
(GeckoView Graveyard :: Sandboxing, task, P1)
Tracking
(firefox75 fixed)
RESOLVED
FIXED
mozilla75
| Tracking | Status | |
|---|---|---|
| firefox75 | --- | fixed |
People
(Reporter: snorp, Assigned: snorp)
References
(Blocks 1 open bug)
Details
(Whiteboard: [geckoview:m75])
Attachments
(1 file)
We kinda accidentally enabled it, but there are some performance concerns.
|
Assignee | |
Updated•5 years ago
|
Assignee: nobody → snorp
Whiteboard: [geckoview:m75]
|
|
Assignee | |
Comment 1•5 years ago
|
||
This was inadvertently enabled and it has memory and likely
other perf impact that we're not yet ready to evaluate.
|
||
Comment 3•5 years ago
|
||
You mean "Socket PROCESS"? :)
|
||
Comment 4•5 years ago
|
||
(Renaming the bug.)
The biggest perf issue that I'm aware of is the fact that launching the socket process is synchronous and blocks the parent process main thread for 190ms+. Profile: https://perfht.ml/3c9MJiP
Blocks: geckoview-startup
Summary: Disable the socket server → Disable the socket process
Pushed by jwillcox@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/fd27c0bf2c4a
Disable the socket server on Android r=kershaw
|
||
Comment 6•5 years ago
|
||
| bugherder | ||
Status: NEW → RESOLVED
Closed: 5 years ago
status-firefox75:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla75
|
||
Comment 7•2 years ago
|
||
Moving socket process bugs to the new GeckoView::Sandboxing component.
Component: General → Sandboxing
|
||
Updated•5 months ago
|
Product: GeckoView → GeckoView Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•