563885 - Fennecs first time startup time is too long

Status: RESOLVED WONTFIX

(Firefox for Android Graveyard :: General, defect)

Description

[Miika Jarvinen]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.1.9) Gecko/20100407 Ubuntu/9.04 (jaunty) Shiretoko/3.5.9 AutoPager/0.5.2.2 (http://www.teesoft.info/)
Build Identifier: 20100503013425

On mobile device first time startup speed is important for end user experience. Currently when nightly Fennec is run on N900 for the first time it takes over 30 seconds to launch. Lots of time is wasted, because Fennec restarts itself on this case (in nsAppRunner). 

If dummy profile is created by first calling Fennec with -createprofile flag, startup time is about ~15 seconds (which still is too much).

Reproducible: Always

Steps to Reproduce:
1. Install nightly Fennec to N900
2. Remove Fennecs profile data by rm -rf /home/user/.mozilla/fennec
3. Start Fennec
Actual Results:  
Fennec startup takes over 30 seconds, and it launches new process during initialization.

Expected Results:  
Startup speed should be faster, and no new process should be launched.

Comment 1

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Mozilla/5.0 (Maemo;Linux armv71; rv:2.0b7pre)Gecko/20100927 Firefox/4.0b7pre Fennec/2.0b1pre

Mozilla/5.0 (Android; Linux armv71; rv2.0b7pre) Gecko/20100927 Firefox/4.0b7pre Fennec/2.0b1pre

Note:
1) Confirmed w/ no profile: 
Maemo takes about ~17 seconds on launch time with a restart of Fennec which makes it appear like it crashes
Android starts up once, but takes about 36 seconds to launch.
2) New User/First Time User Experience Issue; For Android each reinstall will remove the profile.

Comment 2

[Naoki Hirata :nhirata (please use needinfo instead of cc)]

Updated litmus test case:
- https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=12383
Created litmus test case:
- https://litmus.mozilla.org/show_test.cgi?searchType=by_id&id=13527

The timing on how long it should open depends on this bug.  Will update the test cases depending on the outcome of this bug.

Comment 3

[Mark Finkle (:mfinkle) (use needinfo?)]

I don't think we should block on this bug for a few reasons:
* It's not explicit enough about a problem. It's too vague. We can only block on specific bugs.
* We should never be starting Fennec on Maemo from a cold profile. During the install of Fennec on Maemo, we actual launch Fennec using | fennec --silent |, which will create much of the profile folder.

Some parts, like the XUL cache will not be made untilt the UI actually loads, but this should dramatically reduce the startup time.

I would block on a bug that said "Xxx takes Yyy seconds at startup" - something concrete we can tackle.

We should not be doing any restarts anymore. The component registration changes should have fixed that.

I would be interested in seeing any startup profile data. It would definitely help us find the slow code.

Comment 4

[BMO Automation]

Closing all opened bug in a graveyard component