Closed Bug 1560995 Opened 5 years ago Closed 4 years ago

GeckoThread should not wait for process preload

Categories

(GeckoView :: General, task, P2)

Product:
GeckoView
Component:
General
Platform:
Unspecified
Android
Type:
task

Tracking

(firefox68 wontfix, firefox69 wontfix, firefox70 wontfix, firefox71 fix-optional)

Status:
RESOLVED FIXED
Tracking Flags:
Tracking Status
firefox68 --- wontfix
firefox69 --- wontfix
firefox70 --- wontfix
firefox71 --- fix-optional

People

(Reporter: agi, Unassigned)

References

Details

Right now GeckoThread waits until the content process service has started in the code linked below. We shouldn't do that, as we don't need the process immediately at all. Preloading should be asynchronous.

https://searchfox.org/mozilla-central/rev/928742d3ea30e0eb4a8622d260041564d81a8468/mobile/android/geckoview/src/main/java/org/mozilla/gecko/GeckoThread.java#450-459

Type: defect → task
status-firefox68: --- → affected
status-firefox69: --- → affected
Priority: -- → P2
Whiteboard: [geckoview:fenix:m7]

Agi thinks we should not have our own timeout for launching a content process. We should just let Android kill us. Bobby's e10s-multi rewrite (bug 1530770) ought to address this.

status-firefox68: affected → wontfix
status-firefox70: --- → affected
Depends on: android-e10s-multi
OS: All → Android
Whiteboard: [geckoview:fenix:m7] → [geckoview:fenix:m8]
Rank: 33
status-firefox69: affected → wontfix
status-firefox70: affected → wontfix
status-firefox71: --- → fix-optional
Whiteboard: [geckoview:fenix:m8]
Depends on: 1594820
No longer depends on: android-e10s-multi

This should be fixed now.

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