Closed
Bug 1079705
Opened 10 years ago
Closed 10 years ago
~10M AWSY regression on Sept 30
Categories
(Core :: Networking, defect)
Tracking
()
RESOLVED
FIXED
Tracking | Status | |
---|---|---|
firefox34 | --- | unaffected |
firefox35 | + | fixed |
firefox36 | + | fixed |
People
(Reporter: Swatinem, Unassigned)
References
(Blocks 1 open bug)
Details
(Whiteboard: [MemShrink:P1][awsy+][awsy-])
AWSY shows a ~10M regression in the upper "explicit" measurements and in the "heap-unclassified" category.
The "resident" measurement is also up some, but they are very noisy.
![]() |
||
Updated•10 years ago
|
Whiteboard: [MemShrink]
![]() |
||
Updated•10 years ago
|
Whiteboard: [MemShrink] → [MemShrink:P1]
Comment 1•10 years ago
|
||
[Tracking Requested - why for this release]: This is a large regression in memory usage.
status-firefox34:
--- → unaffected
status-firefox35:
--- → affected
status-firefox36:
--- → affected
tracking-firefox35:
--- → ?
![]() |
||
Comment 2•10 years ago
|
||
Drilling down into the heap-unclassified line in the "Miscellaneous Measurements" graph, it's pretty clear that these are the relevant changes:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=946948bfc6a3&tochange=6122db43cad3
So it is bug 1002855. mccr8 backed out a related patch, involving resource timings, in bug 1064706, that was showing up as leaking on e10s builds. He also said that he didn't understand why it was only manifesting on e10s runs; perhaps this is how it was manifesting.
Updated•10 years ago
|
Component: Untriaged → Networking
Updated•10 years ago
|
tracking-firefox36:
--- → +
Comment 3•10 years ago
|
||
I landed bug 1064706, and now we no longer hold refs to the channel in nsPerformanceTiming.
It will be interesting to see how it affects this regression.
![]() |
||
Comment 4•10 years ago
|
||
> I landed bug 1064706, and now we no longer hold refs to the channel in
> nsPerformanceTiming.
> It will be interesting to see how it affects this regression.
I see a clear decrease in the "explicit" and "heap-unclassified" measurements. The size of the decrease is sufficiently close to the original increase that I'm happy to declare victory :)
Thank you for the fix.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Updated•10 years ago
|
Comment 5•10 years ago
|
||
I added annotations to AWSY for this.
Whiteboard: [MemShrink:P1] → [MemShrink:P1][awsy+][awsy-]
You need to log in
before you can comment on or make changes to this bug.
Description
•