Closed Bug 1598759 Opened 4 years ago Closed 1 year ago

Remove the Large-Allocation header (after Fission MVP)

Categories

(Core :: DOM: Content Processes, enhancement, P3)

Product:
Core
Component:
DOM: Content Processes
Platform:
x86
Windows
Type:
enhancement

Tracking

()

Status:
RESOLVED FIXED
Milestone:
100 Branch
Tracking Flags:
Tracking Status
firefox-esr91 --- wontfix
firefox97 --- wontfix
firefox98 --- wontfix
firefox99 --- wontfix
firefox100 --- fixed

People

(Reporter: cpeterson, Assigned: cpeterson)

References

Details

(Keywords: dev-doc-complete, Whiteboard: [fission])

Attachments

(1 file)

Bug 1598759 - Remove support for Large-Allocation HTTP header. r?nika
48 bytes, text/x-phabricator-request
Details | Review

We will disable support Large-Allocation header for Fission in bug 1508306. The header is not widely used and won't be needed when we're forking many content processes with Fission. kmag says we want to remove the header after shipping Fission.

Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → DUPLICATE

I realized this bug is to actually remove the Large Allocation header altogether, not just disable it for Fission.
Removing Fission milestone from this, as this is regardless of Fission.

Status: RESOLVED → REOPENED
Fission Milestone: Future → ---
Resolution: DUPLICATE → ---
Type: task → enhancement
Summary: Disable the Large-Allocation header after Fission MVP → Remove the Large-Allocation header

(In reply to Neha Kochar [:neha] from comment #2)

I realized this bug is to actually remove the Large Allocation header altogether, not just disable it for Fission.
Removing Fission milestone from this, as this is regardless of Fission.

I thought we set Fission Milestone = Future because we wanted to postpone Large-Allocation removal until after we shipped Fission?

Removing Large-Allocation is not part of the Fission project, but Large-Allocation's original rationale is still valid until we do ship Fission.

Fission Milestone: --- → Future
Summary: Remove the Large-Allocation header → Remove the Large-Allocation header (after Fission MVP)

Mochitests related to the large allocation header:
dom/tests/browser/browser_largeAllocation_non_win32.js
dom/tests/browser/browser_largeAllocation_win32.js
dom/security/test/csp/test_reloadInFreshProcess.html

Severity: normal → S4
Fission Milestone: Future → ---
Whiteboard: [fission]
Assignee: nobody → cpeterson
Status: REOPENED → ASSIGNED
status-firefox97: --- → wontfix
status-firefox98: --- → wontfix
status-firefox99: --- → wontfix
status-firefox-esr91: --- → wontfix
OS: Unspecified → Windows
Hardware: Unspecified → x86
Pushed by cpeterson@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/11ba6d0e581f
Remove support for Large-Allocation HTTP header. r=nika,fluent-reviewers

https://hg.mozilla.org/mozilla-central/rev/11ba6d0e581f

Status: ASSIGNED → RESOLVED
Closed: 4 years ago → 1 year ago
status-firefox100: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 100 Branch

Docs work for this can be tracked in https://github.com/mdn/content/issues/14407 - it is mostly complete.

Keywords: dev-doc-needed → dev-doc-complete
You need to log in before you can comment on or make changes to this bug.