Closed
Bug 1191158
Opened 9 years ago
Closed 9 years ago
Promote "Record Allocations" options to no longer experimental option
Categories
(DevTools :: Performance Tools (Profiler/Timeline), defect)
Tracking
(firefox43 fixed)
RESOLVED
FIXED
Firefox 43
Tracking | Status | |
---|---|---|
firefox43 | --- | fixed |
People
(Reporter: jsantell, Assigned: jsantell)
References
Details
Attachments
(1 file)
(deleted),
patch
|
fitzgen
:
review+
|
Details | Diff | Splinter Review |
No description provided.
Assignee | ||
Comment 1•9 years ago
|
||
Attachment #8643428 -
Flags: review?(nfitzgerald)
Comment 2•9 years ago
|
||
Comment on attachment 8643428 [details] [diff] [review]
1191158-alloc-no-experimental.patch
Review of attachment 8643428 [details] [diff] [review]:
-----------------------------------------------------------------
The patch itself is fine, ofc, but some questions:
* Do we have to do anything to remove the Nightly-only restriction? (Does that restriction still exist? Do we want to lift it now as well?)
* Should we wait until we have the byte size columns? (Not sure we have a bug for this, maybe bug 1144423? Bug 1068988 was what added the platform support.)
* Are we ready to commit backwards compat support to old servers that don't have byte sizes (eg the current server) in the future? I'd think that removing the experimental flag signals that this server will be supported in the future.
Attachment #8643428 -
Flags: review?(nfitzgerald) → review+
Assignee | ||
Comment 3•9 years ago
|
||
This experimental flag is the nightly-only restriction (the option still exists, just the UI is hidden in non-nightly for any experimental options).
Uplift is on Monday -- unfortunately bug 1172180 took up most of my life for the release, and unsure if this release can be the "allocations" release that we wanted, or if we should clean it up and make it solid for Fx43, along with JIT Coach. What do you think are all the features needed for this to be "released"? Meta bug at bug 1160812 for tracking allocations things.
It is cutting it uncomfortably close, IMO
Comment 4•9 years ago
|
||
I think the absolute minimum is bytes/percents in bug 1144423 and removing the existing/broken flame graph in bug 1148663.
Also the button to select the relevant time range in bug 1153477.
I'd also really like to see a graph like in bug 1148836, but I think we need to talk about it some more (today?).
Assignee | ||
Updated•9 years ago
|
No longer blocks: perf-tools-fx42
Assignee | ||
Updated•9 years ago
|
Blocks: perf-tools-fx43
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
status-firefox43:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → Firefox 43
Assignee | ||
Comment 7•9 years ago
|
||
Reverting based on discussion in bug 1144423
https://hg.mozilla.org/integration/fx-team/rev/42574a6c75ef
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Comment 9•9 years ago
|
||
Comment 12•9 years ago
|
||
Status: REOPENED → RESOLVED
Closed: 9 years ago → 9 years ago
Resolution: --- → FIXED
Updated•6 years ago
|
Product: Firefox → DevTools
You need to log in
before you can comment on or make changes to this bug.
Description
•