Closed Bug 1442361 Opened 2 years ago Closed Last year

Track content process startup memory in AWSY

Categories

(Core :: General, enhancement)

enhancement
Not set

Tracking

()

RESOLVED FIXED
mozilla62
Tracking Status
firefox62 --- fixed

People

(Reporter: mccr8, Assigned: erahm)

References

(Blocks 2 open bugs)

Details

Attachments

(1 file)

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)
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: Last year
Resolution: --- → FIXED
Target Milestone: --- → mozilla62
You need to log in before you can comment on or make changes to this bug.