It seems like every few months somebody has a shutdown leak problem that only shows up on TBPL, or is on a platform they don't have access to (eg XP). We should add a way to easily dump a compressed CC log to the Tinderbox logs to enable this kind of remote leak debugging. Bill has some patches already to do this, as well as a script to extract the CC logs. We should get that in the tree.
Created attachment 665655 [details] [diff] [review] patch to write out CC logs Here is the main patch I used. Unfortunately, it no longer applies. It piggybacked on some old code to look for DOM window leaks that has been removed. I'm guessing that there must be some way around this, though.
Created attachment 665656 [details] script to extract leak logs This was the corresponding script to extract a CC log from the tryserver log.
Created attachment 667131 [details] [diff] [review] patch to write out compressed CC logs I updated Bill's patch to deal with changes in the test harness.
Assignee: nobody → continuation
Attachment #665655 - Attachment is obsolete: true
Created attachment 667176 [details] script to extract CC logs from tinderbox log I fancied up Bill's script a bit.
Attachment #665656 - Attachment is obsolete: true
Created attachment 667282 [details] script to extract CC logs from tinderbox log, v3 Fixed a stupid error, added some assertions, handle both Windows and Unix style file names.
Attachment #667176 - Attachment is obsolete: true
My first attempt on the Moth leak overflowed the log. I'm trying again with only dumping the third CC. Hopefully that will produce something. Moth is very close to the max log size, but mochitest-chrome is first, so hopefully we can capture it before truncation. https://tbpl.mozilla.org/?tree=Try&rev=8e8e03bd0c23
There's some way to dump files so that you can just download them, which would be better than this.
Status: NEW → RESOLVED
Last Resolved: 3 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.