Add API to junit test harness that enables tests to query for all web content pids
Categories
(GeckoView Graveyard :: Sandboxing, enhancement, P1)
Tracking
(firefox88 fixed)
Tracking | Status | |
---|---|---|
firefox88 | --- | fixed |
People
(Reporter: bugzilla, Assigned: owlish)
References
Details
(Whiteboard: [fission:android:m2] [geckoview:m88] )
Attachments
(1 file, 1 obsolete file)
This is kind of unfortunate, but a consequence of the fact that we have overloaded ContentParent
to be used for multiple types of content.
In GeckoView we'd like to know whether we're being asked to launch a content process for the extension process or web content. Unfortunately, by the time a content process launch request reaches GeckoView code, we do not have that information.
It would be nice if we could have some mechanism to pass ContentParent::mRemoteType
into GeckoChildProcessHost
as a "subtype" so that GeckoView could route the request to create an extension process slightly differently from a normal content process.
The primary issue that we have is that many of our unit tests need to terminate multiple web content processes, but ATM we don't really have a way to distinguish between web and extension content. If there is an alternative way to ascertain this information, I'm all ears, but otherwise we will want to make this change sooner rather than later.
Reporter | ||
Comment 1•4 years ago
|
||
Hmmm, looks like I can probably stuff this info into the aExtraOpts
argument to GeckoChildProcessHost::AsyncLaunch
, so I'll move this into our component.
Reporter | ||
Updated•4 years ago
|
Reporter | ||
Comment 2•4 years ago
|
||
- From Gecko we pass
ContentParent::mRemoteType
intoGeckoProcessManager
for
both process launch and process termination; - We add the extension process as its own service;
- We add the
ContentProcessSubType
enumeration to represent the various
content process subtypes; - We add
GeckoServiceType
that resolves a
(GeckoProcessType, ContentProcessSubType)
tuple into a service name; - We convert
GeckoProcessManager
andServiceAllocator
to work with
GeckoServiceType
instead ofGeckoProcessType
.
Updated•4 years ago
|
Reporter | ||
Comment 3•4 years ago
|
||
This is less important now that the extension process is disabled across the board.
Updated•4 years ago
|
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Reporter | ||
Comment 4•4 years ago
|
||
I think we were planning on bumping this from 78 during sprint planning, but that never made it into the bug.
Reporter | ||
Updated•4 years ago
|
Updated•4 years ago
|
Comment 5•4 years ago
|
||
Tracking this bug for Android Fission milestone M2 (pass tests with Fission enabled).
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
Comment 8•4 years ago
|
||
bugherder |
Comment 9•2 years ago
|
||
Moving isolated process bugs to the new GeckoView::Sandboxing component.
Updated•5 months ago
|
Description
•