Closed Bug 554268 Opened 16 years ago Closed 16 years ago

[e10s] Fennec should start and show UI first, and then initialize child content process

Categories

(Firefox for Android Graveyard :: General, defect)

Product:
Firefox for Android Graveyard
Component:
General
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: romaxa, Unassigned)

References

Details

I'm not sure how it works now, but I think we should initialize fennec UI first and when UI is visible, start content process initialization.
It shouldn't be a tremendous hit right now, seeing as content processes launch asynchronously.
On mobile device we have usually one core, and launching content process at the same time probably will cause slowdown on showing UI content.
what oleg said. right now, you see the chrome process launch really quick, then the "content area" of fennec is very slow to come in. This might be fixed by having us load a chrome page (about:whatever) first.
At least there should not be such a gap in between. I have thought to myself "did I start it or not?" more than once. Some kind of load indicator would be better than nothing. (Of course real content would be best!)
this has been fixed. We startup the UI process, then in the background launch the child content process.
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.