Firefox freezes on Win7 Pro x64 followed by reboot-requiring Windows crash
First, I am a developer myself, so please provide cogent answers.
Since the last few updates (maybe starting with 51) Firefox is presenting with a terrible issue.
When FF has been running for a while (a day or more) with multiple tabs (<20) and I open a new tab using (+) the tab opens (at the 0,0 position, before the silly animation squeezing the other tabs can play) then the parent window shows NOT RESPONDING FF becomes completely non-responsive After several seconds, Win7 windows explorer crashes (as soon as any other windows event is processed, e.g. when trying to start TaskManager, kill the process, switch to another window...etc). At this point, the PC becomes completely unresponsive, mouse freezes, and requires a reboot
Now, a reboot is a major hassle due to sometimes unsaved data loss and mandatory RAID verification.
FF was my favorite browser, with no corporate bloatware. No add-ons except AdBlocker so that I can listen to uTube without the Geico lizard talking in the middle of my fav song. This being a dev machine, there is zero bloatware or crapware, no pron, not even Flash. Just VisualStudio, antivirus, and FF with uTube+AdBlocker for the music.
FF does not even have the time to generate a dump. Not that I let any app send outbound data from this machine. All the "diagnostic instrumentation" from third parties is disabled.
Come on FF devs, you should know what's going on and fix it. Please give me a browser that's simple and does a few things well. Remember KISS from engineering school? Don't force me to switch to Google/Apple/Muscrosoft spyware....
Thank you
All Replies (2)
Problem is still in 54.0.1. I've been watching resources in task manager. It is not related to memory. It is not related to CPU usage. It is not related to TCP connections, although the number seems high to me. This is some sort of hard deadlock, like having non thread-safe code getting an interrupt at just the wrong time. If Mozilla doesn't fix this soon, I'm going to have to switch to Chrome.
MichaelNicholas said
Problem is still in 54.0.1. I've been watching resources in task manager. It is not related to memory. It is not related to CPU usage. It is not related to TCP connections, although the number seems high to me. This is some sort of hard deadlock, like having non thread-safe code getting an interrupt at just the wrong time. If Mozilla doesn't fix this soon, I'm going to have to switch to Chrome.
My gut feel - from observing the behavior of Windows during the crash - is that window events get generated in an endless loop somewhere (or some similar overflow of windows resources is being used, e.g. creation of device contexts or something like that)
Modified by AmityGames