Last Comment Bug 648415 - about:memory doesn't report on the plugin processes
: about:memory doesn't report on the plugin processes
Status: RESOLVED WONTFIX
[MemShrink:P2]
:
Product: Core
Classification: Components
Component: Plug-ins (show other bugs)
: unspecified
: All All
: -- normal with 3 votes (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
:
: Benjamin Smedberg [:bsmedberg]
Mentors:
Depends on: revampaboutmemory
Blocks: MemShrinkTools
  Show dependency treegraph
 
Reported: 2011-04-07 16:38 PDT by Nicholas Nethercote [:njn]
Modified: 2012-04-17 17:31 PDT (History)
17 users (show)
See Also:
Crash Signature:
(edit)
QA Whiteboard:
Iteration: ---
Points: ---
Has Regression Range: ---
Has STR: ---


Attachments

Description Nicholas Nethercote [:njn] 2011-04-07 16:38:05 PDT
about:memory doesn't report any information for the plugin-container process.  We probably can't report much info for it, but some basics (eg. the amount of mapped and resident memory) would be nice.  (If we can do more, that would be nice.)

about:memory already handles the separate chrome and content processes for Fennec, so the infrastructure is already present for reporting for multiple processes.  It just needs to be hooked up to the plugin-container process.
Comment 1 Chris Jones [:cjones] inactive; ni?/f?/r? if you need me 2011-04-07 22:03:15 PDT
(We use the plugin-container process for all subprocess types.  Yeah, sigh.)  I think for this bug you're referring to the subprocesses in which plugin code runs.

We can quite easily forward jemalloc, gfxASurface, and shmem stats from plugin processes.
Comment 2 Nicholas Nethercote [:njn] 2011-04-08 00:27:11 PDT
(In reply to comment #1)
> I think for this bug you're referring to the subprocesses in which plugin code
> runs.

Probably, I don't have the terminology down :)

> We can quite easily forward jemalloc, gfxASurface, and shmem stats from plugin
> processes.

That'd be great!
Comment 3 Nicholas Nethercote [:njn] 2012-04-17 17:31:29 PDT
You can get the basic numbers like resident from the OS pretty easily.  This doesn't seem worth the effort.

Note You need to log in before you can comment on or make changes to this bug.