Closed Bug 1562761 Opened 5 years ago Closed 5 years ago

Bind the Android process launcher to a single owner thread

Categories

(Core :: IPC, task, P2)

task

Tracking

()

RESOLVED FIXED
mozilla72
Tracking Status
firefox71 --- wontfix
firefox72 --- fixed

People

(Reporter: bholley, Assigned: bholley)

References

Details

(Whiteboard: [geckoview:m1911])

Attachments

(1 file)

Our current setup for process launching on Android involves the IPC machinery dispatching via a thread pool and invoking a synchronous process launch method in Java. That Java machinery then uses explicit synchronization to avoid data races.

I don't think this setup is going to scale well to lots of concurrent process launches and service reuse. The Right Way to do this is to have an owner thread, and replace the current blocking bits with asynchronous callbacks. I'm working on this during my free moments.

Depends on: 1562762
Priority: -- → P2
Depends on: 1566583
Depends on: 1566592

Aaron says he will be working on this bug in November.

Assignee: bholley → aklotz
Whiteboard: [geckoview:m1911]

Correction: Bobby wrote this patch. Aaron says he's just submitting the patch for review.

Assignee: aklotz → bholley
Summary: Bind the android process launcher to a single owner thread → Bind the Android process launcher to a single owner thread
Pushed by aklotz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/efc82f89a7c7
Add support for dispatching java runnables to Gecko event targets. r=snorp

I'll take it.

Flags: needinfo?(bholley)
Pushed by aklotz@mozilla.com:
https://hg.mozilla.org/integration/autoland/rev/e552592bceae
Add support for dispatching java runnables to Gecko event targets. r=snorp

firefox71=wontfix because we don't need to uplift this runnable fix to GeckoView Beta (71).

Status: NEW → RESOLVED
Closed: 5 years ago
Resolution: --- → FIXED
Target Milestone: --- → mozilla72
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: