702486 - Startup takes 20 seconds to complete

Status: RESOLVED INVALID

(Firefox for Android Graveyard :: General, defect)

Description

[Julien Vermet | JulienDev]

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.7; rv:11.0a1) Gecko/20111112 Firefox/11.0a1
Build ID: 20111112031541

Steps to reproduce:

I launched Fennec ( build 11/15/2011 ) on my Galaxy S (i9000).
Cyanogenmod 7 (Android 2.3)


Actual results:

1. Fennec is launching & The layout is displayed immediately
2. I can access the AwesomeBar, AwesomeScreen, Menu... BUT I can't request a page until 20 seconds

On the logcat you can see I took 20 seconds to complete the startup
http://pastebin.mozilla.org/1382464

During the first 20 seconds, I can request a page, the favicon let me think the page is loading but at the end of the startup the website stop loading and I get the Home page.


Expected results:

The app should load faster.

Comment 1

[Julien Vermet | JulienDev]

In my opinion the issue comes from libxul library who takes 16 seconds to load on Galaxy S (i9000).

I compared the results to those obtained on my HP Touchpad (Cyanogenmod 7 - Android 2.3) and the same library it only takes 4 seconds

HP Touchpad Logcat : http://pastebin.mozilla.org/1382525

Comment 2

[(dormant account)]

There is a bug in certain non-stock firmwares. If you look at the numbers, the bug is not in fennec.

11-15 01:43:46.090: E/GeckoLibLoad(1211): Loaded libs in 15596ms total, 1191ms user, 453ms system, 23 faults
11-15 01:43:46.090: E/GeckoLibLoad(1211): Spent 431ms on relocations, 7ms on constructors

16seconds spend loading libraries...only 1191ms of those spent in the fennec process. 432ms(!!! in the kernel). Either some userlevel cpu hog or a kernel bug is causing this. pwalton observed this on some custom galaxy s firmware, other apps like the launcher were also starting slow.

Comment 3

[Doug Turner (:dougt)]

kevin, do you still have contacts at cyanogenmod?

Comment 4

[Julien Vermet | JulienDev]

I tried with a Galaxy S (i9000) with stock firmware (2.3.3 JVH)
http://pastebin.mozilla.org/1383233
It takes 13 seconds to load the library. So, the problem doesn't come from CM7

New links for previous logcat pastebin :
i9000 CM7 : http://pastebin.mozilla.org/1382560
Touchpad CM7 : http://pastebin.mozilla.org/1382559

Comment 5

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

This seems completely in line with the crappy file system on the Galaxy S.

Comment 6

[Lucas Rocha (:lucasr)]

(In reply to Mark Finkle (:mfinkle) from comment #5)
> This seems completely in line with the crappy file system on the Galaxy S.

True. But 16s is a bit too bad, even for a Galaxy S. On my Galaxy S, it usually takes 4-6 seconds for Gecko to start.

Comment 7

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

(In reply to Lucas Rocha (:lucasr) from comment #6)
> (In reply to Mark Finkle (:mfinkle) from comment #5)
> > This seems completely in line with the crappy file system on the Galaxy S.
> 
> True. But 16s is a bit too bad, even for a Galaxy S. On my Galaxy S, it
> usually takes 4-6 seconds for Gecko to start.

Agreed. I just mean that we have known about this for a while now, from XUL Fennec. It's not a shocking discovery.

There is work happening to make startup in general faster. I don't think this particular bug is something we need to work on separately.

Comment 8

[Julien Vermet | JulienDev]

(In reply to Mark Finkle (:mfinkle) from comment #7)
> (In reply to Lucas Rocha (:lucasr) from comment #6)
> > (In reply to Mark Finkle (:mfinkle) from comment #5)
> > > This seems completely in line with the **** file system on the Galaxy S.
> > 
> > True. But 16s is a bit too bad, even for a Galaxy S. On my Galaxy S, it
> > usually takes 4-6 seconds for Gecko to start.
> 
> Agreed. I just mean that we have known about this for a while now, from XUL
> Fennec. It's not a shocking discovery.
> 
> There is work happening to make startup in general faster. I don't think
> this particular bug is something we need to work on separately.

I agree with you, the orginal filesystem is **** on GS. Maybe I'm wrong but if I remember well, CM7 use a lagfix based on ext4 filesystem instead of RFS filestystem in order to avoid this problem.

Comment 9

[(dormant account)]

(In reply to Mark Finkle (:mfinkle) from comment #5)
> This seems completely in line with the crappy file system on the Galaxy S.

It's completely not. CM7 uses ext4. It's not letting fennec use any cpu because something else is stealing it. This is a ROM bug. if someone could do some oprofiling they'd see that something is seriously wrong with the ROM.

Comment 10

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

(In reply to Taras Glek (:taras) from comment #9)
> (In reply to Mark Finkle (:mfinkle) from comment #5)
> > This seems completely in line with the crappy file system on the Galaxy S.
> 
> It's completely not. CM7 uses ext4. It's not letting fennec use any cpu
> because something else is stealing it. This is a ROM bug. if someone could
> do some oprofiling they'd see that something is seriously wrong with the ROM.

Comment 4 says this was happening on a stock ROM

Comment 11

[(dormant account)]

(In reply to Mark Finkle (:mfinkle) from comment #10)

> Comment 4 says this was happening on a stock ROM

My fault. Sounds like an actionable item. It doesn't look like a filesystem bug. Looks like java ui might be stealing cpu cycles.

Comment 12

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

Julien, would it be possible for you to try a build from 11/09/2011?
http://ftp.mozilla.org/pub/mozilla.org/mobile/nightly/2011-11-09-04-05-05-birch-android/fennec-10.0a1.en-US.android-arm.apk

Link shortened: http://goo.gl/SCaKC

I suspect that there might be a slow down from 11/11 ~ 11/12 build.

Comment 13

[Julien Vermet | JulienDev]

11/09/2011 : http://pastebin.mozilla.org/1383505 > 4 seconds
11/15/2011 : http://pastebin.mozilla.org/1383506 > 10 seconds

So, you're right, there is a slow down.

And I also have a problem with my builds. Mine seems more verbose and slower.
My mozconfig : http://pastebin.mozilla.org/1383509

Comment 14

[Julien Vermet | JulienDev]

Ok, I

1. deleted my objdir

2. removed
ac_add_options --enable-debug
ac_add_options --disable-optimize
from mozconfig

3. compiled again, waited one hour

4. saw I was installing an old release (10 instead of 11)
5. ran it, and everything is ok, startup takes 4 seconds

Stupid Julien

Comment 15

[Doug Turner (:dougt)]

ignoring that.. :p

There are two pastebin's.  The first shows us loading a startup image via the old GeckoSurfaceView.  The second shows us loading a similar image via the new compositor system.  The difference is that in the new system we save out a bigger png (so that we can pan it around a bit more).

It could be that is causing some difference.  blassey has patches to delay the loading a bit.  That will help.

Comment 16

[(dormant account)]

(In reply to Doug Turner (:dougt) from comment #15)
> ignoring that.. :p
> 
> There are two pastebin's.  The first shows us loading a startup image via
> the old GeckoSurfaceView.  The second shows us loading a similar image via
> the new compositor system.  The difference is that in the new system we save
> out a bigger png (so that we can pan it around a bit more).
> 
> It could be that is causing some difference.  blassey has patches to delay
> the loading a bit.  That will help.

can we report time to load the png on commandline + telemetry?