1473410 - login taking longer on usbank.com, bankofamerica.com, chase.com

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[Ajay Gupta]

User Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0
Build ID: 20180704100142

Steps to reproduce:

login is taking longer on many bank sites I use - usbank.com, bankofamerica.com, and chase.com, to name a few popular ones. Since logins do succeed eventually, I would guess there is some glitch in the handshaking protocol.


Actual results:

Logins taking longer than usual.


Expected results:

Login should be almost instantaneous (as they used to be).

Comment 1

[Rares Doghi, Desktop QA]

Hi, Please test if the issue is reproducible in safe mode, here is a link that can help you:
https://support.mozilla.org/en-US/kb/troubleshoot-firefox-issues-using-safe-mode

Also is this issue reproducible in chrome or other browsers as well?

Comment 2

[Ajay Gupta]

The issue is reproducible in Firefox Nightly in Safe Mode.

I tried these websites with Chromium Browser just now and the issue was not seen. One other related data-point is that Chromium reports a shorter DNS Latency time (15ms) in contrast to Firefox Nightly (25ms). This could explain the slow response in Firefox Nightly. I am not sure what I can do to fix the DNS Latency in Firefox Nightly.

Comment 3

[Ajay Gupta]

Not sure why or how, but the Nightly  performance has improved significantly today. My user agent is: "Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:63.0) Gecko/20100101 Firefox/63.0".  The changes I have made so far are:
1. Increase the initial pagefile.sys file to 4GB, with a max of 8GB (it was automatically controlled before and was hovering around 2GB).
2. Disable the OCSP check in the Nightly.
3. Upgrade the Windows 10 OS to the latest insider build, 18204.

I am sure someone would chime in the real reason for this performance boost.

Comment 4

[Rares Doghi, Desktop QA]

Hi,I will mark this issue as Resolved WORKS FOR ME, since it no longer occurs, please Reopen this issue if it re-occurs.