After reboot, tabs are blank, pages won't load, Firefox won't close.
I've switched to Windows 10 recently, and I've been struggling with a very weird bug in all versions of Firefox:
Sometimes, when I open Firefox after a reboot, all saved tabs appear blank, I can't load any new pages or make searches, and Firefox won't close normally and I have to kill the process. It's really weird, so I made a gif: http://i.imgur.com/S1a8WXX.gif
I've tried all of the following, to no avail: - using the standard, developer and nightly versions. - repairing Firefox - deleting the profile - disabling the antivirus - disabling Smart Screen - reinstalling Windows 10 altogether
Just leaving the name of the executable to anything else than "firefox" seems to prevent the bug from reappearing. I have mine set to "firefix.exe", and after a few reboots, it is still working. I don't know how this could make any sense...
Update: When I run the bugged firefox.exe with the -console argument, I get the following output: https://pastebin.com/hZ90jRbz
Whereas when I launch the working firefix.exe, it only prints the first two lines.
Được chỉnh sửa bởi Victor vào
Tất cả các câu trả lời (2)
I managed to narrow down the problem, but it's getting even more mysterious to me:
Just replacing the executable by a copy of itself solves the issue, until the next reboot. The copy is in all aspects identical to the original. Same size, same permissions, same attributes. All I do is click-drag-copy the executable in the program folder, rename the old one to "firefox old.exe", rename the copy to "firefox.exe". The "firefox old.exe" executable keeps displaying the same weird behavior, while the new one, although identical, works. Until I reboot. Then I have to do the same steps again.
I've posted a question on the Microsoft Community support forum.
Does anyone have an idea on how to diagnose this?
Actually, portable version 55.0.2 (64bit) from portableapps and installed ESR version 52.3.0 (64bit) are not affected.
Also, with Firefox Developer Edition, just leaving the name of the executable to anything else than "firefox" seems to prevent the bug from reappearing. I have mine set to "firefix.exe", and after a few reboots, it is still working. I don't know how this could make any sense...