Closed
Bug 726201
Opened 14 years ago
Closed 14 years ago
Lazy load about:home
Categories
(Firefox for Android Graveyard :: General, defect, P2)
Tracking
(firefox13 verified, fennec12+)
VERIFIED
FIXED
People
(Reporter: sriram, Assigned: sriram)
Details
(Keywords: perf)
If there is no session to restore, the about:home is kicked off from the Java itself and loads on startup. This takes around 1 to 1.5 seconds usually. Instead, we can wait for the Gecko to ask Java to load about:home. Thereby we won't be stalling the main thread on startup, and the app comes up much faster.
Comment 1•14 years ago
|
||
This will be a balancing act. We don't necessarily want to wait for Gecko to be ready before showing the AboutHome page. That could take >3 seconds. We _do_ want to make sure that the AboutHome code is not delaying the initial UI from displaying, but AboutHome should load ASAP afterward.
Updated•14 years ago
|
Assignee: nobody → sriram
tracking-fennec: ? → 12+
Priority: -- → P2
Assignee | ||
Comment 2•14 years ago
|
||
As a part of the patch in bug 725932, I am lazy loading the about:home if we are not doing a session restore. This happens when Gecko is loading in the background (or probably I might need to profile it a bit and move chunks of code to do it ;) ). This way, we don't wait for Gecko, but still lazy load about:home.
Assignee | ||
Comment 3•14 years ago
|
||
Fixed as a part of bug 725932.
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Comment 4•13 years ago
|
||
Verified fixed on:
Firefox 13.0a1 (2012-03-01)
20120301031135
http://hg.mozilla.org/mozilla-central/rev/1c3b291d0830
--
Device: Samsung Galaxy S2
OS: Android 2.3.4
Status: RESOLVED → VERIFIED
status-firefox13:
--- → verified
Updated•5 years ago
|
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•