WANT_ALL_TRACES cycle collector dumps are nice because they have more information about the heap, but they don't provide an accurate picture of what the cycle collector does, which might be important when remotely diagnosing cycle collector performance problems. One way to implement this would be to have a boolean property on a listener that says whether it wants WANT_ALL_TRACES or not, then have the constructor for the default dumping listener have an optional argument that sets the property.
I think I'm just going to add an additional pref in bug 668225 to control whether dumps are WANT_ALL_TRACES or not. My original idea was to expose it to JS so we could ask people to use a different magic invocation of the CC dump, but generally I'd like to get away from people using that and towards using a config, so we get avoid Heisenberg problems.
Status: NEW → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 668225
Wrong dup bug num?
Ah, thanks. Man, I am not doing well with bug numbers today.
Duplicate of bug: 688225
You need to log in before you can comment on or make changes to this bug.