Closed Bug 1260582 Opened 6 years ago Closed 10 months ago

Investigate GeckoProfile initialization in onCreate


(Firefox for Android Graveyard :: General, defect)

Not set


(Not tracked)



(Reporter: mcomella, Unassigned, Mentored)



In onStart, there is a comment explaining we don't want to init GeckoProfile too soon (presumably for disk access issues). However, in onCreate, we do the same checks.

We should either:
* move the initial checks off the main thread
* Remove the comment from onStart
* Remove the comment from onStart and push the check onto the UIThread

Profiling recommended. :)
15:21 <mcomella> rnewman: I think we init the profile in onCreate (, before we do that queue to the bg thread to prevent profile init too early (, so I
15:21 <mcomella> don't think the comment is correct. Am I missing something?

15:31 <@rnewman> mcomella: I think checking whether we were a guest profile used to be really expensive
15:31 <@rnewman> added here:
15:32 <@rnewman> mcomella: but also we didn't used to do any profile stuff in onCreate:
15:33 <@rnewman> mcomella: so yes, if you've moved profile init into onCreate, then (a) that might account for our startup time regression this quarter, and (b) that comment is inaccurate :P
FYI, GeckoProfile does its expensive init in GeckoProfile.forceCreate, which is called when the GeckoView is initialized in layout.
We have completed our launch of our new Firefox on Android. The development of the new versions use GitHub for issue tracking. If the bug report still reproduces in a current version of [Firefox on Android nightly]( an issue can be reported at the [Fenix GitHub project]( If you want to discuss your report please use [Mozilla's chat]( server and join the [#fenix]( channel.
Closed: 10 months ago
Resolution: --- → INCOMPLETE
Product: Firefox for Android → Firefox for Android Graveyard
You need to log in before you can comment on or make changes to this bug.