On desktop, the content process pretty much always crashes before it gets a chance to report leaks. If we fix the crash, then leaks appear. It seems most reasonable to disable content process leak checking, fix the crashes, and eventually fix the leaks and re-enable.
Kyle, what effect will that have on your b2g work?

Comment on attachment 8477089[details][diff][review]
Disable leak checking in content processes.
Review of attachment 8477089[details][diff][review]:
-----------------------------------------------------------------
::: build/automationutils.py
@@ +353,5 @@
> return
>
> # totalBytesLeaked was seen and is non-zero.
> + # For now, ignore tab process leaks. See bug 1051230.
> + if (totalBytesLeaked > leakThreshold) and (not processType or processType != "tab"):
so we will still get a warning printed. Can we somehow indicate in the log file in the else condition below that we are ignoring this as it is a tab process?