The default bug view has changed. See this FAQ.

about:memory doesn't report on the plugin processes

RESOLVED WONTFIX

Status

()

Core
Plug-ins
RESOLVED WONTFIX
6 years ago
5 years ago

People

(Reporter: njn, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [MemShrink:P2])

(Reporter)

Description

6 years ago
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.
(Reporter)

Updated

6 years ago
Keywords: uiwanted
OS: Mac OS X → All
Hardware: x86 → All
(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.
Component: IPC → Plug-ins
QA Contact: ipc → plugins
Summary: about:memory doesn't report on the plugin-container process → about:memory doesn't report on the plugin processes
(Reporter)

Comment 2

6 years ago
(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!
(Reporter)

Updated

6 years ago
Whiteboard: [MemShrink:P2]
(Reporter)

Comment 3

5 years ago
You can get the basic numbers like resident from the OS pretty easily.  This doesn't seem worth the effort.
Status: NEW → RESOLVED
Last Resolved: 5 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.