We should add a section to the about:memory that lists the data from the child process
This is going to be interesting. about:memory uses nsIMemoryReporter, which just has a couple accessors that return values on demand. Since the numbers come from the content process, we can't just synchronously ask for them. Therefore, we either: * update the parent reporters at regular intervals, when we won't actually care about them 99% of the time * introduce a "priming" phase into the memory reporter manager, such that nsMemoryReporterManager::EnumerateReporters actually traverses the array and pokes each reporter in case it needs to get ready. Then we race to see if we can get a value from content just in time to show it! Any other ideas are welcome, too.
The other bug has a patch, so duping forward.