Create leak log more lazily
Categories
(Core :: XPCOM, task)
Tracking
()
People
(Reporter: mccr8, Unassigned)
References
Details
(Whiteboard: [MemShrink:P2])
One way to make us more resilient against the kind of failures in bug 1615072 would be to create the leak log more lazily. Right now, we create it early in process startup, but we don't write anything to it until we shut down. I think this is simply because for other kinds of logs, like refcount logs, we do need to start it up immediately. If we waited until we actually needed to write to the log, then the process type would be set up correctly.
One thing to watch out for would be making sure that we still catch failures to create logs when a process crashes before shutdown.
It would make it a little more annoying to figure out what test was running when we wrote out the log, but I think it'll just take a little more work, because you have to look earlier in the log.
Updated•3 years ago
|
Description
•