Closed
Bug 539989
Opened 15 years ago
Closed 3 years ago
Object visualization tool
Categories
(Core :: JavaScript Engine, enhancement)
Tracking
()
RESOLVED
INACTIVE
People
(Reporter: gwagner, Unassigned)
Details
Since we want to test several GC strategies for JS and identify bottleneck of the current GC, we should have some kind of visualization tool. The idea is to generate heap snapshots before/after a GC and write this (maybe filtered) information to a file. Visualization tools that read XML files are around. Visualization properties could be age, arena group, connections....
Reporter | ||
Updated•15 years ago
|
Assignee: general → mozilla
Comment 1•15 years ago
|
||
JSON >> XML for such things...
/be
Reporter | ||
Updated•15 years ago
|
Assignee: mozilla → maierfg
Comment 2•13 years ago
|
||
Is this still relevant as a non-TM bug?
Comment 3•13 years ago
|
||
(In reply to Ryan VanderMeulen from comment #2)
> Is this still relevant as a non-TM bug?
Yes, though I don't see it going anywhere soon. Gregor, want to close it?
Summary: TM: Object visualization tool → Object visualization tool
Comment 4•13 years ago
|
||
With bug 680482, we can dump a textual representation of the GC heap. It shouldn't be too hard to modify my CC heap visualization script to do the same for GC, but that is fairly crude, so I'm not sure if you could do anything about age or arena groups.
Reporter | ||
Comment 5•13 years ago
|
||
We have an outdated implementation but we might rebase it.
Comment 6•13 years ago
|
||
At JSConf.eu, I have seen such a tool being used during Erik Corry's presentation (from the Chrome team). So such a tool already exists and it may be a matter of feeding its API. I don't know where it is though.
Changing the summury, because if you want a tool to visualize objects, it's a different thing. (I have started one at http://davidbruant.github.com/ObjectViz/ )
Summary: Object visualization tool → Heap visualization tool
Comment 7•13 years ago
|
||
With the renaming of this bug it looks awfully similar to bug 670594. That one has some old code, it was for visualizing at a very high level -- chunks and arenas. Sounds like this bug is about more fine-grained visualization. The names should be changed to reflect this.
Reporter | ||
Comment 8•13 years ago
|
||
Nick already has a bug about heap visualization. This bug is about a finer granularity where we can look at individual objects.
Summary: Heap visualization tool → Object visualization tool
Comment 9•3 years ago
|
||
The bug assignee didn't login in Bugzilla in the last 7 months.
:sdetar, could you have a look please?
For more information, please visit auto_nag documentation.
Assignee: maierfg → nobody
Flags: needinfo?(sdetar)
Comment 10•3 years ago
|
||
- mccr8's tools contain scripts for processing the GC heap dump now, in addition to the CC heap dump tools. I don't think there's anything for visualization, though.
- The Memory tab in devtools has a rather nice display of the various types of objects in the heap, though it seems pretty limited in interaction, filtering, etc.
- about:memory serves some part of this need.
- we have various profiling output that dumps out some information
The intent of this bug seems to be more about something that would help tune the GC. We still have that need. Whether a visualization tool would be an important part of that, I'm not sure.
Closing. If we decide we need something like this, it'd probably be better to start a new bug. The information in the comments here is stale.
Status: NEW → RESOLVED
Closed: 3 years ago
Flags: needinfo?(sdetar)
Resolution: --- → INACTIVE
You need to log in
before you can comment on or make changes to this bug.
Description
•