Closed Bug 1218975 Opened 9 years ago Closed 9 years ago

FF 40.xx LOCKS UP ENTIRE WIN7 GUI WHILE LOADING SPECIFIC SITES

Categories

(Core :: Graphics, defect)

40 Branch
defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 624005

People

(Reporter: jessijames52, Unassigned, NeedInfo)

Details

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:39.0) Gecko/20100101 Firefox/39.0 Build ID: 20150806001005 Steps to reproduce: On first boot up or even subsequent RANDOM launches of FF in the same session loading specific sites will lock up FF and the entire GUI for approx 20-30 seconds. Happens CONSISTENTLY when loading FACEBOOK login page Actual results: The WIN7 Ultimate GUI is rendered inoperative while FF does whatever its doing for 20-30 (sometimes more) seconds. No input via keyboard is possible or input via pointing device is possible at these times of lockup. Expected results: WIN7 should be totally responsive and while FF is doing its thing loading ANYTHING the OS GUI should be freely available for input.
I have ROLLED BACK to FF version 39.0.3 and the problem above has subsided. I have disabled any automated updating for the FF browser and have disabled any attempts for the browser update/change any installed plugins. In short this is working as it should now and I will not allow it to move forward with any further updates until the issue above is corrected.
This seems to be related to the issue I listed in bug 1122939 - NOW after rolling back to 39.0.3 if I click OFF the Hardware Acceleration box to get rid of the on screen artifacting the LOCKUP issue happens anyway. I had no problems at all prior to I believe version 37.x. And as I stated before there is no updateable driver for the machine in question.
Component: Untriaged → Graphics
Product: Firefox → Core
Version: 39 Branch → 40 Branch
Does the issue happen in a clean profile?
Flags: needinfo?(jessijames52)
Status: UNCONFIRMED → RESOLVED
Closed: 9 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.