Closed Bug 1590614 Opened 5 years ago Closed 1 year ago

Slow Start up. (6 Seconds)

Categories

(Toolkit :: Startup and Profile System, defect, P5)

68 Branch
Desktop
Windows
defect

Tracking

()

RESOLVED WORKSFORME
Tracking Status
firefox-esr68 - ---
firefox70 --- wontfix
firefox71 --- wontfix
firefox72 --- affected

People

(Reporter: seanas80, Unassigned)

Details

(Keywords: perf, Whiteboard: [fxperf:p5])

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Start firefox.

Actual results:

It took 6 seconds to start up.

Expected results:

Before it was 1-2 seconds before Version 68.2. I have been using esr but it seems the time has run out and now I have to face 68.2 which is really slow at starting up even on an SSD. I have tried everything from installing fresh with a new profile. Repairing. Everything you could think of.

My environment is as follows:
OS:
Windows 7 Ultimate

Hardware:
Motherboard: ATX Format - ASUS Rampage IV Extreme
Chipset - X79 & LGA-2011
CPU: Intel Core i7 3820
RAM: GSkill Ripjaws Z Series 1600
GPU: Nvidia GTX 1080

Storage:
OS/Main: Samsung 840 EVO SSD
Secondary: Toshiba HDWD120 HDD
Auxiliary: Seagate ST4000DM004 HDD

(In reply to seanas80@hotmail.co.uk from comment #0)

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:68.0) Gecko/20100101 Firefox/68.0

Steps to reproduce:

Start Firefox on Win 7 x64.

Actual results:

It took 6 seconds to start up.

Expected results:

Before it was 1-2 seconds before Version 68.2. I have been using esr but it seems the time has run out and now I have to face 68.2 which is really slow at starting up even on an SSD. I have tried everything from installing fresh with a new profile. Repairing. Everything you could think of.

Has STR: --- → no
Keywords: perf

Hello,

I was able to reproduce this issue using the 68.2.0 esr build, the release 70.0, the beta 71.0b4 and Nightly 72.0a1 (2019-10-28) on Windows 7 and Windows 10 x64.
On Windows 7 it took around 6-6.5 seconds for the firefoxes to open, while on Windows 10 it takes about 5-5.5 .

Does this issue occur on beta/release/nightly as well? Could you please test on these versions as well?

I will set a component for this bug in order to get the dev team involved.
If it's not the correct one, feel free to change it to an appropriate one.

Status: UNCONFIRMED → NEW
Component: Untriaged → Startup and Profile System
Ever confirmed: true
Flags: needinfo?(seanas80)
Product: Firefox → Toolkit

Thank you very much for reproducing this issue. I have always sworn by firefox and always will but i cannot put up with it take 6 seconds to come up. I did not want to betray but I was using a Mozilla fork Waterfox.

Just very recently now I went to Waterfox after the issue and now it also suffers the same issue after its update. It has adopted the new code and has the same 6 second loading time on starting up like firefox.. This really needs fixing. This is a browser showstopper. Nobody wants to wait more than 2 seconds for their browser to appear and I swear by Firefox. I really wish this will get fixed. Thank you.

Flags: needinfo?(seanas80)

The priority flag is not set for this bug.
:mossop, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dtownsend)

(In reply to Andrei Purice from comment #3)

Hello,

I was able to reproduce this issue using the 68.2.0 esr build, the release 70.0, the beta 71.0b4 and Nightly 72.0a1 (2019-10-28) on Windows 7 and Windows 10 x64.
On Windows 7 it took around 6-6.5 seconds for the firefoxes to open, while on Windows 10 it takes about 5-5.5 .

What was actually reproduced here? Are those numbers significantly different to previous releases of Firefox?

Flags: needinfo?(dtownsend) → needinfo?(andrei.purice)

Hello Dave,

While previously testing this issue I was opening Firefox using Profile Manager.
Upon deleting the profiles and opening Firefox as a normal user would it only takes 1.2 seconds for it to launch.

Sean, can you please let us know if you were also opening using Profile Manager?
Also can you tell us what antivirus you're using?

Flags: needinfo?(andrei.purice) → needinfo?(seanas80)

(In reply to Andrei Purice from comment #7)

Hello Dave,

While previously testing this issue I was opening Firefox using Profile Manager.
Upon deleting the profiles and opening Firefox as a normal user would it only takes 1.2 seconds for it to launch.

Ok, that would probably make this bug 1553399.

Hello again, I can confirm that I am using Avast Premium Security. i have tested running FireFox with it disabled and with the Avast plugins completely removed from FireFox.

I can also confirm that when I use profiles to launch another instance of FireFox it seems to load fast and normally. I have tested running in various profiles still on (current beta/release).

If I was to start another instance of FireFox however (another process) in windows normally It will still take the average 6 seconds to load but for some reason not when FireFox is directly told to launch a new instance via the about:profiles menu which is interesting..

Flags: needinfo?(seanas80)

The priority flag is not set for this bug.
:mossop, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dtownsend)

Ok I'm pretty sure this is tied up in the same locking issues as bug 1553399.

Status: NEW → RESOLVED
Closed: 5 years ago
Flags: needinfo?(dtownsend)
Resolution: --- → DUPLICATE
Severity: normal → critical
Status: RESOLVED → REOPENED
OS: Unspecified → Windows
Priority: -- → P4
Resolution: DUPLICATE → ---

Firefox >66 Slow start up even without the profile manager. This can be related to bug 1553399 but is still in my eyes actually a branch of the similar problem. I feel that this should remain looked into thank you.

I am willing to run some more tests in order to confirm this. But how would one run the latest Firefox with profiles completely disabled? Do you think this would be an adequate workaround?

(In reply to Andrei Purice from comment #7)

Hello Dave,

While previously testing this issue I was opening Firefox using Profile Manager.
Upon deleting the profiles and opening Firefox as a normal user would it only takes 1.2 seconds for it to launch.

Sean, can you please let us know if you were also opening using Profile Manager?
Also can you tell us what antivirus you're using?

I have deleted all profiles but the main profile that I use now and can confirm the issue is still the same. I have Firefox version 66 installed which uses this profile and it starts up fast and normal 1.2 seconds.

For the newest Firefox though it does not and even when deleting my main profile and using a fresh one with the new Firefox it still does the same over 6 seconds start up, Profile or not. I had backed up my main profile to test this.

Component: Startup and Profile System → Launcher Process
Product: Toolkit → Firefox
Hardware: Unspecified → Desktop
Component: Launcher Process → Startup and Profile System
Product: Firefox → Toolkit

The product::component has been changed since the backlog priority was decided, so we're resetting it.
For more information, please visit auto_nag documentation.

Priority: P4 → --

adding -no-remote to the command line fixed the issue

The priority flag is not set for this bug.
:mossop, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(dtownsend)

No point looking into this until bug 1553399 is figured out.

Flags: needinfo?(dtownsend)
Priority: -- → P5
Whiteboard: [fxperf]

I agree with comment 17, we need to look at bug 1553399 first.

If there's a good reason to think the problem is different here, having a startup profile of the problem would be interesting. https://developer.mozilla.org/en-US/docs/Mozilla/Performance/Profiling_with_the_Built-in_Profiler#Profiling_Firefox_Startup

Whiteboard: [fxperf] → [fxperf:p5]

Bug 1553399 has been fixed, so presumably this is fixed too? Are you still able to reproduce?

Severity: critical → --
Status: REOPENED → NEW
Flags: needinfo?(seanas80)

Redirect a needinfo that is pending on an inactive user to the triage owner.
:mossop, since the bug has recent activity, could you have a look please?

For more information, please visit auto_nag documentation.

Flags: needinfo?(seanas80) → needinfo?(dtownsend)

Please reopen if this is reproducible with latest nightlies as we have fixed a couple of issues with startup locks since this bug was last reproduced.

Status: NEW → RESOLVED
Closed: 5 years ago1 year ago
Flags: needinfo?(dtownsend)
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.