Closed
Bug 849280
Opened 11 years ago
Closed 11 years ago
[Browser] Long initial startup time for Browser app
Categories
(Firefox OS Graveyard :: Gaia::Browser, defect)
Tracking
(blocking-b2g:tef+, b2g18 verified, b2g18-v1.0.1 verified)
VERIFIED
FIXED
blocking-b2g | tef+ |
People
(Reporter: mbudzynski, Assigned: mbudzynski)
References
Details
(Whiteboard: [FFOS_perf])
Attachments
(1 file)
160 bytes,
text/html
|
benfrancis
:
review+
akeybl
:
approval-gaia-v1+
|
Details |
With avg of 1.2s its the second slowest app in Gaia now.
Assignee | ||
Updated•11 years ago
|
Summary: [Browser] Long initial startup for Browser app → [Browser] Long initial startup time for Browser app
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → mbudzynski
Assignee | ||
Comment 1•11 years ago
|
||
Attachment #722855 -
Flags: review?(bfrancis)
Comment 2•11 years ago
|
||
bug 843852 may be related
Comment 3•11 years ago
|
||
Comment on attachment 722855 [details]
patch
r=me
Attachment #722855 -
Flags: review?(bfrancis) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Thanks Ben. Merged: https://github.com/mozilla-b2g/gaia/commit/e3e313b236ccc8a389c7cf53b10959d7aef2ed88
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Updated•11 years ago
|
Comment 5•11 years ago
|
||
Michal, can you tell us what is the perf gain with this patch ?
Flags: needinfo?(mbudzynski)
Comment 6•11 years ago
|
||
note: this will need Bug 841251 uplifted before uplifting this.
Depends on: 841251
Comment 8•11 years ago
|
||
(for v1.0.1, I think we are generally content with the browser app start time so passing this along to leo? for consideration)
blocking-b2g: tef? → leo?
Another reason to have this nomed and uplifted. bug 849917 is fixed for v1 train if this lands in v1 train.
Comment 10•11 years ago
|
||
Comment on attachment 722855 [details] patch NOTE: Please see https://wiki.mozilla.org/Release_Management/B2G_Landing to better understand the B2G approval process and landings. [Approval Request Comment] Bug caused by (feature/regressing bug #): - User impact if declined: browser starts slower AND Bug 849917 is still there Testing completed: yes Risk to taking this patch (and alternatives if risky): the patch is not the safest (changes in the lazy loader) but it was tested and it landed for 1 week in master already. + there are unit tests for the added functionality in lazy_loadder.js String or UUID changes made by this patch: none
Attachment #722855 -
Flags: approval-gaia-v1?
Updated•11 years ago
|
Attachment #722855 -
Flags: approval-gaia-v1? → approval-gaia-v1?(bfrancis)
Comment 11•11 years ago
|
||
Bug 836647 is tef+ and needs to be uplifted to 1.0.1, but that patch introduces a regression which is fixed by this bug. Without this fix we can not uplift bug 836647, so should this bug be tef+ too?
blocking-b2g: leo? → tef?
Comment 12•11 years ago
|
||
Comment on attachment 722855 [details]
patch
Approving for v1.1 given perf wins - would recommend against uplift to v1.0.1.
Attachment #722855 -
Flags: approval-gaia-v1?(bfrancis) → approval-gaia-v1+
Comment 13•11 years ago
|
||
If this is not tef+ then bug 836647 can not be tef+ because uplifting it would cause a regression.
Comment 15•11 years ago
|
||
I've uplifted this to v1-train myself now that it has approval because it has merge conflicts that needed resolving, and because it fixes a regression caused by uplifting bug 836647 which needed fixing sooner than later. https://github.com/mozilla-b2g/gaia/commit/7af427d35c4d557c75b2060022815f07851acc28 Still not uplifted to v1.0.1
Comment 16•11 years ago
|
||
Ben, don't forget to set the flags when you uplift ;)
status-b2g18:
--- → fixed
Comment 17•11 years ago
|
||
What does status-b2g18: fixed mean? Is that how you flag something as fixed on Gaia v1-train?!
Comment 18•11 years ago
|
||
yes ;)
Comment 19•11 years ago
|
||
(In reply to Ben Francis [:benfrancis] from comment #15) > https://github.com/mozilla-b2g/gaia/commit/ > 7af427d35c4d557c75b2060022815f07851acc28 > > Still not uplifted to v1.0.1 Is this uplift something that you'd be able to take care of? There are lots of conflicts that I am not sure how to resolve.
Comment 20•11 years ago
|
||
e3e313b236ccc8a389c7cf53b10959d7aef2ed88 uplifted to v1.0.1 as d8c844c8b89bb453b49c7a4107686bf97050e985
status-b2g18-v1.0.1:
--- → fixed
Updated•11 years ago
|
tracking-b2g18:
? → ---
Comment 21•11 years ago
|
||
No need to create a test case in Moztrap for this issue.
Flags: in-moztrap-
Comment 22•11 years ago
|
||
Verified fixed in Unagi V1 and V.1.01: according to the "show time to load" setting in the Developer screen, the load time is 475 Unagi V1 Unagi Build ID: 20130401070203 Kernel Date: Dec 5 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18/rev/f9f11b8cbf8a Gaia: 663101b6eb809383e5882d9bc3868a923a57998a Unagi build V.1.0.1 Unagi Build ID: 20130401070203 Gecko: http://hg.mozilla.org/releases/mozilla-b2g18_v1_0_1/rev/b28463f2e718 Gaia: ddb38ac8a34f9e30e09d0ff3b5c1bfb9b664b7c3
Comment 23•11 years ago
|
||
I doubt the load time is 475. I believe you tried to launch it while it was already loaded. The correct STR to measure the startup time of an app is : * long press the home button * kill any instance of the app * press home to go back to homescreen * launch the app 6 seconds must have elapsed since the last launch.
You need to log in
before you can comment on or make changes to this bug.
Description
•