Closed Bug 1067491 Opened 10 years ago Closed 10 years ago

Add allocation profiling to the memory actor

Categories

(DevTools :: Memory, defect)

x86
macOS
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED FIXED
Firefox 35

People

(Reporter: fitzgen, Assigned: fitzgen)

References

Details

Attachments

(1 file, 1 obsolete file)

Splitting this out from my work in bug 960671 for use in bug bug 1066361.
Assignee: nobody → nfitzgerald
Status: NEW → ASSIGNED
Attached patch memory-actors.patch (obsolete) (deleted) — Splinter Review
jryans, this is the same actor patch(es) you reviewed in bug 960671, but I just want to rubber stamp it again since it is in a new bug now. I split the toggling of recording into a start and stop method, as you asked. This is a combined patch of the allocations changes, the force GC/CC changes, and a tiny method exposing Debugger.Memory.prototype.takeCensus over the RDP. It was getting too hard to keep everything separate, sorry. https://treeherder.mozilla.org/ui/#/jobs?repo=try&revision=cba18023568c
Attachment #8489689 - Flags: review?(jryans)
Comment on attachment 8489689 [details] [diff] [review] memory-actors.patch Review of attachment 8489689 [details] [diff] [review]: ----------------------------------------------------------------- Still seems good to me!
Attachment #8489689 - Flags: review?(jryans) → review+
Unless you're checking this in yourself, I think you should add a commit message to the patch.
Flags: needinfo?(nfitzgerald)
Flags: needinfo?(nfitzgerald)
Keywords: checkin-needed
Whiteboard: fixed-in-fx-team
Whiteboard: fixed-in-fx-team → [fixed-in-fx-team]
sorry had to back this out for test failures like https://tbpl.mozilla.org/php/getParsedLog.php?id=48249937&tree=Fx-Team
Whiteboard: [fixed-in-fx-team]
Hrm, I can't repro locally. Digging into the test logs...
Attached patch memory-actors.patch (deleted) — Splinter Review
Ok just adding a check that the frame does exist in test_memory_allocations_01.html. Let's see how this turns out: https://tbpl.mozilla.org/?tree=Try&rev=d00453950900
Attachment #8489689 - Attachment is obsolete: true
Attachment #8490879 - Flags: review+
And I just realized I didn't include mochitest-chrome in that try push. Sigh...
Looks like adding that null check fixed it!
Keywords: checkin-needed
Blocks: 1066313
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 35
Depends on: 1070107
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: