900259 - Add a way to dump both a normal and an AllTraces CC log in B2G

Status: RESOLVED WONTFIX

(Core :: XPCOM, defect)

Description

[Andrew McCreight [:mccr8]]

Right now we get a GC log and an all-traces CC log, but it might be nice to get a non-all-traces CC log as well.  It won't always be useful, but it sometimes will, and just having everything produced with a single script makes it easier when getting reports from random people, especially when this is for tests that take days to run, and thus aren't easily reproduced.  The regular CC log should also be pretty tiny, so it shouldn't be a big deal to add.

Some issues I can think of off the top of my head:
- We don't want multiple GC logs, because those are huge.  Right now, we always produce a GC log when we produce a CC log, so we'll need some way to control that.
- Name the CC log so that we don't lose the nice correspondence between the GC log name and the CC log name.
- For the regular log, we probably want to make sure that ForgetSkippable() gets run at least a few times, or we can end up with weird issues where if it is called at the wrong time we don't clean up everything we could.

This will require some work to set up the CC to log in this way, and then additional minor changes to make MemoryInfoDumper produce the right thing.

Comment 1

[Olli Pettay [:smaug][[e-mail]]]

nsJSContext::CycleCollectNow makes sure ForgetSkippable is run at least NS_MAJOR_FORGET_SKIPPABLE_CALLS times, unless that is explicitly disabled.

Comment 2

[Andrew McCreight [:mccr8]]

Thanks, I'd forgotten that.