959634 - TabsPanel.<init> can be expensive during startup

Status: RESOLVED DUPLICATE of bug 909550

(Firefox for Android Graveyard :: General, defect)

Description

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

Even though the TabsPanel is not shown during startup, it is initialized and accounts for 2.5% (~130ms).

Let's investigate why we are initializing the TabsPanel during startup. Make sure we don't regress things like bug 848070.

profile: http://people.mozilla.org/~mfinkle/fennec/profiles/nexuss-home-startup.trace

Comment 1

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

Also shows up in GalaxyNexus startup profile (~5%, ~140ms)

profile: http://people.mozilla.org/~mfinkle/fennec/profiles/galaxynexus-home-startup.trace

Comment 2

[:Margaret Leibovic]

We include the TabsPanel in the gecko_app layout:
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/resources/layout/gecko_app.xml#11

We can probably be lazier about the things we're doing in the TabsPanel constructor though. We're doing a lot in there:
http://mxr.mozilla.org/mozilla-central/source/mobile/android/base/TabsPanel.java#68

Comment 3

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

Shilpan started work in bug 909550