Open Bug 1222593 Opened 9 years ago Updated 2 years ago

Allocation Stack view numbers are wrong after reloading page

Categories

(DevTools :: Memory, defect, P2)

defect

Tracking

(firefox45 affected)

Tracking Status
firefox45 --- affected

People

(Reporter: wbamberg, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(2 files)

Attached image memory-tool-bug-1.gif
STR:
(1) open a new tab
(2) load https://mdn.github.io/performance-scenarios/dom-allocs/alloc.html
(3) open the Memory tool
(4) select "Record allocation stacks"
(5) reload the page
(6) take a snapshot
(7) switch to "Allocation Stack" view

I get a total size of about 6MB, with about 75-80% inside "alloc.js".

Now reload the page, and take a new snapshot. Now the new snapshot shows me a total size of less that 2MB, with 80% of that marked "(no stack available)"

Now, in the second snapshot, switch to the "Coarse Type" view. Now the second snapshot reports 6MB. Switching back to "Allocation Stack" and it goes back to ~2MB.

See the attachment "memory-tool-bug-1.gif" for this.

***

Now switch to the first snapshot, using the sidebar on the left. The main window now looks wrong: the "Total Bytes" no longer adds up to 100%, and the entry for "alloc.js" is not at about 3%.

Now, switch to the second snapshot. In the main window, "Total Bytes" now sums to much more than 100% ("alloc.js" is now at around 350%!).

It looks like the percentages and totals for the two snapshots have become confused. This seems like it might be a different bug.

See the attachment "memory-tool-bug-2.gif" for this.
Attached image memory-tool-bug-2.gif
Has STR: --- → yes
Priority: -- → P2
Product: Firefox → DevTools
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: