Closed
Bug 384942
Opened 18 years ago
Closed 18 years ago
dump graph on cycle collection fault
Categories
(Core :: XPCOM, enhancement)
Tracking
()
RESOLVED
FIXED
People
(Reporter: graydon, Assigned: graydon)
Details
Attachments
(1 file)
|
4.68 KB,
patch
|
dbaron
:
review+
|
Details | Diff | Splinter Review |
When the cycle collector hits a fatal fault (in a DEBUG build, with DEBUG_CC defined at compile time and XPCOM_CC_FAULT_IS_FATAL at runtime), it's nice to get a dump of the current collection graph with the offending node highlighted.
Attachment #268850 -
Flags: review?(dbaron)
Comment on attachment 268850 [details] [diff] [review]
patch to write out a graph highlighting the offending node on a fatal fault
Looks good, but 2 thoughts:
* why not just set sCurrGraph in GCGraph's ctor and dtor?
* seems like it would be useful even if faults aren't fatal
r=dbaron
Attachment #268850 -
Flags: review?(dbaron) → review+
| Assignee | ||
Comment 2•18 years ago
|
||
Checked in with fix to use GCGraph ctor/dtor.
It's easy enough to toggle fatality at runtime, and I'd imagine if you have DEBUG on you won't notice a CC fault amongst all the debug chatter.
new revision: 1.51; previous revision: 1.50
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → FIXED
Updated•18 years ago
|
Flags: in-testsuite-
You need to log in
before you can comment on or make changes to this bug.
Description
•