Closed
Bug 1352359
Opened 7 years ago
Closed 7 years ago
We should peg the file content process to just one process initially
Categories
(Core :: DOM: Content Processes, enhancement)
Core
DOM: Content Processes
Tracking
()
VERIFIED
FIXED
mozilla55
| Tracking | Status | |
|---|---|---|
| firefox55 | --- | verified |
People
(Reporter: bobowen, Assigned: bobowen)
Details
(Whiteboard: sbwc2, sbmc2, sblc3)
Attachments
(1 file)
|
1.01 KB,
patch
|
gkrizsanits
:
review+
|
Details | Diff | Splinter Review |
Given that it probably has much more limited use, I think we should keep to just one file content process, at least initially.
|
Assignee | |
Comment 1•7 years ago
|
||
This is just following-up on that dev-platform thread, although it seemed to die out. We also discussed this at the sandboxing meeting and decided we should keep it to one initially. MozReview-Commit-ID: 2KDYLhr8U6W
Attachment #8853358 -
Flags: review?(gkrizsanits)
|
||
Comment 2•7 years ago
|
||
Comment on attachment 8853358 [details] [diff] [review] Set dom.ipc.processCount.file to 1 Review of attachment 8853358 [details] [diff] [review]: ----------------------------------------------------------------- Makes sense to me.
Attachment #8853358 -
Flags: review?(gkrizsanits) → review+
Pushed by bobowencode@gmail.com: https://hg.mozilla.org/integration/mozilla-inbound/rev/cf4ce9f1b829 Set dom.ipc.processCount.file to 1. r=gabor
|
||
Comment 4•7 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/cf4ce9f1b829
Status: ASSIGNED → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla55
|
||
Comment 5•7 years ago
|
||
Verified as fixed on the latest Nightly 55.0a1 (Build ID: 20170523030206) - per Default, there is only one file content process allocated for the local files. Verified on Windows 10 x64, Ubuntu 16.04 x64 and Mac OS X 10.12
Status: RESOLVED → VERIFIED
You need to log in
before you can comment on or make changes to this bug.
Description
•