Closed Bug 1579553 Opened 6 years ago Closed 6 years ago

firefox hangs when attempting to access amazon in a clean profile

Categories

(Core :: Graphics: Text, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1575315

People

(Reporter: mattliley, Unassigned)

Details

(Keywords: perf)

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

Steps to reproduce:

i went to amazon.co.uk and attempted to interact with page elements

Actual results:

the browser hangs for around 10-15 seconds before the keyboard input appears in the search bar. no other elements on the website are accessible or can be interacted with during this time. firefox can still scroll through the site.

i recorded the issue using the gecko profiler. here's the link: https://perfht.ml/2ZFBsUI

Expected results:

amazon.co.uk should be responsive immediately

thank you, the problem appears to be caused my malwarebytes anti-exploit on your system that's hooking into the browser - please try again without it being present.

Component: Untriaged → Other
Product: Firefox → External Software Affecting Firefox
Version: 68 Branch → unspecified

i have uninstalled the offending application and restarted the computer. the issue appears to be still present. the performance monitor shows a setTimeout event with a duration of 13,431ms - if you'd like more information about this i will happily provide.

i have recorded a new version of the issue post malwarebytes AE uninstall - https://perfht.ml/2ZMgQuc

thanks for the update, so with mbae out of the equation the process seems to have become a bit quicker but the hang is still over 10 secs long. what appears to be happening is that firefox is cycling through all the fonts present on the system while attempting to render a particular character, so i'll move the report to a better component.

Component: Other → Graphics: Text
Keywords: perf
Product: External Software Affecting Firefox → Core

This looks like bug 1575315, for which a patch landed in Fx70. We should perhaps consider uplifting to 69 as well.

Status: UNCONFIRMED → RESOLVED
Closed: 6 years ago
Resolution: --- → DUPLICATE

Oh, wait... 69 is release now, isn't it. So the fix is already in beta, which is as good as we can do for now, I think.

You need to log in before you can comment on or make changes to this bug.