FF 67 slow start (5 seconds)

[xerces8]

I noticed that my FF takes very long to start.

I created a new profile and after doubleclicking it in the profile manager, it takes 5 seconds before the FF window appears.
Before it was around one second.
By before I mean " a few days ago", I do not know exactly.

Anyone else seeing this?

I have Windows 8.1 Pro 64 bit.

[malliz]

Why not make a new clean profile make it the default and see if the normal starting procedure is slow? Going through the profile manager to start a profile I would think will slow things down

[therube]

There's a bug (or feature, depending on how you look at things ) for that.

5-second lag on each opening new Firefox window from command line on all concurrent FF users except first since machine boot.
https://bugzilla.mozilla.org/show_bug.cgi?id=1553829


(Seems that like Microsoft, Mozilla does not do any actual testing.
They simply throw [..]it out there & wait for the crap to hit the fan.)

[xerces8]

Thanks! Hope they release a fixed version soon...

[James]

(Seems that like Microsoft, Mozilla does not do any actual testing.
They simply throw [..]it out there & wait for the crap to hit the fan.)

Then what are the Beta channel and Release Candidate builds for then

[therube]

Oh, lets bump this.

Up till today, I thought it was still lingering bugs related to profilemania, but now, while it still may be, I'm thinking it is not any yet identified bugs?
Or at least there is something on my end causing this to continue to manifest itself - when opening a Profile from Profile Manager.


So today, I put in Windows updates (cough, kind of like FF updates), so in doing so had to reboot my computer (not typical).
With that done, I fire up FF, from Profile Manager, & it's slow.

I did not expect that.

In the past, I typically have other browsers open, including an ancient FF 3.0 which I use as the back-end from ChatZilla (XULrunner).
And I'd always thought it was that FF (which is "always" open) which was causing FF 67 to be so slow to open.

But on computer restart, no other FF was running, nor any other browsers, nor much of anything else, yet FF was still slow to open.

On my end, this has persisted ever since FF 67, & up to today's Nightly (70).

I've removed profiles.ini, installs.ini, created new Profile, all to no result.

Win7 x64, FF 70 x64.
i5-3570K, 16 GB RAM, & while the machine is relatively dated at this point, it is clean, & runs well (as it always has).
No A/V or anything like that. No Window Defender, not even the "malware tool" (anymore).
(Just whatever spyware, ahem, "telemetry" MS [Mozilla] {quietly} installed.)

Windows theme (I use "Classic", XP-like) is not the issue (tested using default Windows 7 theme).

Opening FF using either -profile or -p is speedy.
Only Profile Manager is slow.

Code: Select all

firefox.exe -profile PROFILENAME
firefox.exe -p  NIGHTLY_PROFILE


Bugs point to %TMP%/firefox (& firefox/parent.lock).
(My %TMP% is relocated [from default location on E: to C:].)
And I can see the directory/file being created & deleted, only much slower when using Profile Manager.


Nirsoft: FolderChangesView - Monitor files changes on Windows

Using -p or -profile, created, deleted, within 1 second:

Code: Select all

==================================================
Filename          : firefox
Modified Count    : 1
Created Count     : 1
Deleted Count     : 1
Renamed Count     : 0
Full Path         : C:\Local\RUBEN\Temp\firefox
Extension         :
File Owner        : RUBEN7\RUBEN
First Event Time  : 07/20/2019 01:13:15 PM
Last Event Time   : 07/20/2019 01:13:15 PM
File Size         :
Modified Time     : 07/20/2019 01:13:15 PM
Created Time      : 07/20/2019 01:13:15 PM
Entry Modified Time: 07/20/2019 01:13:15 PM
Attributes        : DI
==================================================

==================================================
Filename          : parent.lock
Modified Count    : 0
Created Count     : 1
Deleted Count     : 1
Renamed Count     : 0
Full Path         : C:\Local\RUBEN\Temp\firefox\parent.lock
Extension         : lock
File Owner        : RUBEN7\RUBEN
First Event Time  : 07/20/2019 01:13:15 PM
Last Event Time   : 07/20/2019 01:13:15 PM
File Size         : 0
Modified Time     : 07/20/2019 01:13:15 PM
Created Time      : 07/20/2019 01:13:15 PM
Entry Modified Time: 07/20/2019 01:13:15 PM
Attributes        : AI
==================================================


using Profile Manager, takes multiple seconds:

Code: Select all

==================================================
Filename          : firefox
Modified Count    : 1
Created Count     : 1
Deleted Count     : 1
Renamed Count     : 0
Full Path         : C:\Local\RUBEN\Temp\firefox
Extension         :
File Owner        : RUBEN7\RUBEN
First Event Time  : 07/20/2019 01:06:30 PM
Last Event Time   : 07/20/2019 01:06:40 PM
File Size         :
Modified Time     : 07/20/2019 01:06:30 PM
Created Time      : 07/20/2019 01:06:30 PM
Entry Modified Time: 07/20/2019 01:06:30 PM
Attributes        : DI
==================================================

==================================================
Filename          : parent.lock
Modified Count    : 0
Created Count     : 1
Deleted Count     : 1
Renamed Count     : 0
Full Path         : C:\Local\RUBEN\Temp\firefox\parent.lock
Extension         : lock
File Owner        : RUBEN7\RUBEN
First Event Time  : 07/20/2019 01:06:30 PM
Last Event Time   : 07/20/2019 01:06:40 PM
File Size         : 0
Modified Time     : 07/20/2019 01:06:30 PM
Created Time      : 07/20/2019 01:06:30 PM
Entry Modified Time: 07/20/2019 01:06:30 PM
Attributes        : AI
==================================================


Ideas?



Wonder if Thunderbird is/will be affected similarly?
I'd hope it would use a different %TMP% dirname.

[therube]

security only

I wish, New Windows 7 'security-only' update installs telemetry/snooping.
(Anyhow, at least, for whatever reason, I've never had any sort of Win10 "upgrade" prompt.)


[all right, where did it go? did you delete it or did a moderator. sure wish people would leave things alone. edits aside.]

[therube]

"Screenshot", 1.3 MB .gif, https://i.postimg.cc/vYnHHVqF/FF67-5-se ... r.gif?dl=1 (download).

[therube]

installs.ini:

Code: Select all

[D4D64138A454E275]
Default=C:\TMP\SEA\52.9\NIGHTLY
Locked=1

[8A92B18FED63327C]
Default=C:\TMP\SEA\52.9\PROFILE67
Locked=1



profiles.ini

Code: Select all

[InstallD4D64138A454E275]
Default=C:\TMP\SEA\52.9\NIGHTLY
Locked=1

[Profile1]
Name=NIGHTLY
IsRelative=0
Path=C:\TMP\SEA\52.9\NIGHTLY

[Profile0]
Name=PROFILE67
IsRelative=0
Path=C:\TMP\SEA\52.9\PROFILE67
Default=1

[General]
StartWithLastProfile=0
Version=2

[Install8A92B18FED63327C]
Default=C:\TMP\SEA\52.9\PROFILE67
Locked=1



compatibility.ini

Code: Select all

[Compatibility]
LastVersion=70.0a1_20190720095435/20190720095435
LastOSABI=WINNT_x86_64-msvc
LastPlatformDir=C:\WLIB\FIREFOX\FIREFOX
LastAppDir=C:\WLIB\FIREFOX\FIREFOX\browser



[therube]

So I take it that no one ever uses Profile Manager to open FF.

From what I can see, it is simply buggered, still.

FF 68, on a different Win7 & on a Win10 show the same symptoms.
Significant delay when opening a profile from Profile Manager compared to opening via other means.

Code: Select all

firefox.exe  -profilemanager  --->  select existing Profile from list
                                    (& wait)
firefox.exe  -p       PROF68  --->  PROF68 being an existing profile already defined in Profile Manager
                                    (opens speedily)
firefox.exe  -profile  C:\TMP\NEWPRO  --->  NEWPRO being a newly created Profile Folder in C:\TMP
                                            (opens speedily)


[therube]

I guess this (at this point) is the pertinent bug:
Bug 1553399 Firefox start slowly when started through ProfileManager.


And this pretty much tells it all:

Given that we don't expose the profile manager or consider it primary UI, this gets fxperf:p3 if that.

Sad.

So Profile Manager is not even to be considered a "feature" of FF.

Really Sad.

And for some common sense:

As for priority, this issue literally ruins the efforts of making Firefox start as fast as possible. It is now painful to start Firefox.

But this being Mozilla, common sense does not apply.
Sigh.


(Wonder why I didn't find this bug in my earlier searches?)