Closed Bug 1149245 Opened 10 years ago Closed 9 years ago

DeserializedEdgeRange should re-use its referents edge vector (not copy it)

Categories

(DevTools :: Memory, defect)

x86
macOS
defect
Not set
normal

Tracking

(firefox45 fixed)

RESOLVED FIXED
Firefox 45
Tracking Status
firefox45 --- fixed

People

(Reporter: fitzgen, Assigned: fitzgen)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

(In reply to Jim Blandy :jimb from bug 1024774 comment #165) > ::: toolkit/devtools/server/DeserializedNode.cpp > @@ +165,5 @@ > > + return false; > > + } > > + > > + DeserializedNode &referent = node.getEdgeReferent(*edgep); > > + edges.append(mozilla::Move(SimpleEdge(name, Node(&referent)))); > > It's a pity we have to copy the edge vector like this. Could you file a > follow-up bug to make this iterate over the DeserializedNode's underlying > vector, and have 'settle' build a proper JS::ubi::Edge from the current > element?
Assignee: nobody → nfitzgerald
Has STR: --- → irrelevant
Status: NEW → ASSIGNED
Comment on attachment 8683285 [details] [diff] [review] Make DeserializedEdgeRange re-use its referents edge vector Review of attachment 8683285 [details] [diff] [review]: ----------------------------------------------------------------- This looks solid, but I don't claim to know the existing heapsnapshot code that well. If you're having doubts about whether or not this fits into the grand scheme of things, please check with Jim too.
Attachment #8683285 - Flags: review?(vporof) → review+
Status: ASSIGNED → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 45
Product: Firefox → DevTools
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: