Closed
Bug 1385736
Opened 7 years ago
Closed 5 years ago
How to distinguish between content processes and Extension OOP processes?
Categories
(Core :: IPC, enhancement, P2)
Core
IPC
Tracking
()
RESOLVED
FIXED
People
(Reporter: yfdyh000, Unassigned)
References
(Blocks 1 open bug)
Details
I can see "gpu" for GPU process - command line from Process Explorer and about:memory, but how to confirm which process is the Extension OOP process? Because I see 5 + 1 (main process) processes have 100+MB memory usage, as dom.ipc.processCount is 4. I want to investigate how much memory is used from extensions, and check the pid from about:memory. Therefore, I suggest the process list - command line, about:memory and about:performance annotate the nature of the processes.
Blocks: webext-oop
(In reply to YF (Yang) from comment #0) > Therefore, I suggest the process list - command line, about:memory and > about:performance annotate the nature of the processes. Note: I guess this should be done with multiple bugs, so this bug is a question for confirmation.
Once bug 1383978 lands, you'll be able to look in about:memory.
(In reply to Bill McCloskey (:billm) from comment #2) > Once bug 1383978 lands, you'll be able to look in about:memory. Thanks.
Depends on: 1383978
Updated•7 years ago
|
Component: General → IPC
Product: Firefox → Core
Updated•7 years ago
|
Status: UNCONFIRMED → NEW
Ever confirmed: true
Priority: -- → P2
Comment 4•5 years ago
|
||
As far as I can see this is fixed. about:memory displays the pid of the WebExtensions process as mentioned in comment 2 and the process is now also titled "WebExtensions" in the system process explorer.
Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•