Hello. I have been using Firefox off-and-on since the version 2.0, and there has been one bug that is plaguing me since 10+ years, and that is this error message that occ… (tuilleadh eolais)
Hello. I have been using Firefox off-and-on since the version 2.0, and there has been one bug that is plaguing me since 10+ years, and that is this error message that occurs when I close down Firefox and try to immediately reopen it (sometimes I wait 2-3 seconds just to avoid this error to no avail).
I am using version 65.0.2 (x64) now on latest Windows 10 version (on an MSI laptop with a spec of Intel i7 8750H cpu, Kingston SSD, 16 gb dual channel RAM and Nvidia RTX 2070 graphics card) and have been encountering this bug daily, and it really became so annoying that I'm considering reverting back to Chrome (which NEVER had this bug). This problem usually occurs when my previous Firefox session had more than 4 or so tabs, etc. but it also occurs when I just try to close and reopen the Firefox to test if the bug persists and 1 out of 5 times I get this bug and have to wait around 10 seconds for Firefox to realize there is a leftover session and offer me to close it before being able to open a new tab/window.
I have tried removing the .lock file from the profile folder (which DOES NOT remove itself when I end my session and gets recreated each time I restart a session), checking off the read-only mark from the profile folder, creating another profile and disabling hardware accelerating; but none of these made the slightest impact on the frequency I experience this problem. This thread from official Mozilla support also didn't help (https://support.mozilla.org/en-US/kb/firefox-already-running-not-responding ).
Should I just accept that this is the way Firefox works and that I need to wait 5-6 sec or so before attempting to reopen Firefox (as suggested here https://www.howtogeek.com/131004/how-to-fix-the-firefox-is-already-running-error/ (which dates back to 2012 and saddens me deeply that 7 more years of development changed nothing on this front)), or shut the Firefox down each time by killing it from the Task Manager; or could there maybe a fix to this? I had recently ditched Chrome since it froze my computer (a very rare bug related to the newer Windows 10 versions which occured only once to me, but felt serious enough that I uninstalled it), but if I can't find a reliable fix to this problem, I will probably just go back to Chrome where the bugs won't affect my daily usage.
Thank you for your help.