Closed Bug 1442361 Opened 7 years ago Closed 6 years ago

Track content process startup memory in AWSY

Categories

(Core :: General, enhancement)

Product:
Core
Component:
General
Type:
enhancement
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED
Milestone:
mozilla62
Tracking Flags:
Tracking Status
firefox62 --- fixed

People

(Reporter: mccr8, Assigned: erahm)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

Track explicit memory usage in the base content memory test
(deleted), patch
mccr8
: review+
Details | Diff | Splinter Review
Maybe we already do this, but if we're going to put in a bunch of work to shave off 100kb here and there of memory, we should track it so we know about regressions. What we want is content process startup memory (eg without any real content loaded).
Andrew, is the about:blank test good enough for this? It measures: - Base Content Resident Unique Memory - Base Content Heap Unclassified - Base Content JS I guess we could add explicit as well.
Flags: needinfo?(continuation)
Yeah, that sounds fine.
Flags: needinfo?(continuation)
Attachment #8986927 - Flags: review?(continuation)
Assignee: nobody → erahm
Status: NEW → ASSIGNED
Attachment #8986927 - Flags: review?(continuation) → review+
https://hg.mozilla.org/integration/mozilla-inbound/rev/9253a827f52d262efee2f659095d38cf0b44fd0f Bug 1442361 - Track explicit memory usage in the base content memory test. r=mccr8
https://hg.mozilla.org/mozilla-central/rev/9253a827f52d
Status: ASSIGNED → RESOLVED
Closed: 6 years ago
status-firefox62: --- → fixed
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: