Closed
Bug 1177115
Opened 9 years ago
Closed 9 years ago
[Raptor] Introduce configurable delay between application fullyLoaded and memory capture
Categories
(Firefox OS Graveyard :: Gaia::PerformanceTest, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
FxOS-S2 (10Jul)
People
(Reporter: Eli, Assigned: Eli)
References
Details
Attachments
(1 file)
We need a way to trigger a GC before capturing memory results, so in the meantime, we are going to introduce a configurable delay between fullyLoaded and mozdevice memory capture trigger.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8625775 -
Flags: review?(rwood)
Comment 2•9 years ago
|
||
Comment on attachment 8625775 [details] [review] Link to Github pull-request: https://github.com/mozilla-b2g/gaia/pull/30701 LGTM and works great, just suggest adding a message in the console indicating an intentional delay is happening so that it doesn't look like raptor has stalled unintentionally.
Attachment #8625775 -
Flags: review?(rwood) → review+
Updated•9 years ago
|
Target Milestone: --- → FxOS-S2 (10Jul)
Comment 3•9 years ago
|
||
Can this land now?
Assignee | ||
Comment 4•9 years ago
|
||
In master: https://github.com/mozilla-b2g/gaia/commit/f62941f64136e6c0d6fa67003a0459fbbcfdf973
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•