9

0

20

Mac OS X High Sierra 10.13.6
Here's the routine with FF on this machine: If FF 68.0.2 is running, after a while I will try to open a new tab and be told "Sorry we need to… (ulteriori informazioni)

Mac OS X High Sierra 10.13.6

Here's the routine with FF on this machine: If FF 68.0.2 is running, after a while I will try to open a new tab and be told "Sorry we need to do one small thing to keep going, FF has been updated in the background, Restart FF" I do so. It opens up a new, clean profile in a new window (About FF now says 68.0.1 in this version of FF, and it downloads 68.0.2 and prompts to Restart FF (again)). At which point it runs "a new helper tool" and re-updates FF to 68.0.2. I then have to mess with about:profiles to go back to my profile. Things then run routinely for a few hours or a day, before the whole routine starts over again.

Alternately, if FF 68.0.2 is not running, if I open it (after opening and closing it several times without issue), I will get a message that "You've launched an older version of FF, Create New Profile or Quit". Create New Profile leads me through the routine above.

Versions of the above routine have happened not just between 68.0.2 and 68.0.1, but also between earlier version updates. That is, this has been going on for months. It does seem in the last couple of weeks that the interval of time has shortened and I'm having to do this routine everyday or even multiple times a day. I have no problems like this with FF on any other machine.

I've tried:

Trashing FF and re-dl'ing from Mozilla. No dice.
Trashing FF, trashing Library/Cache/Mozilla and Firefox folders. No dice.
Trashing FF, trashing Library/Application Support/Firefox/Profiles (and re-signing in to retrieve my existing bookmarks etc and re-setting up View and other Preferences). No dice.

Why is Firefox not writing a new file when I open or close a tab? Is there anything I can do right now do get diagnostics on this problem? I believe that tomorrow I may be installing Windows patches and have to reboot, and restarting Firefox will lose all diagnostic data. Thanks.

when I launch ff it just hangs forever showing white screen
I have to kill that last tab before ff snaps into action ... it make no matter what was
that last active tab prior to killing ff on launch it repeatedly shows just white screen

6

2

15

I have created a extension for Gmail. I added that to firefox and the extesion has aded but the problem is after refreshing or reopening i have reload extension also othe… (ulteriori informazioni)

I have created a extension for Gmail. I added that to firefox and the extesion has aded but the problem is after refreshing or reopening i have reload extension also otherwise it won't work, what is the problem? i have attached 2 images that is one before reloading the extension and 2nd is after reloading the extension.

3

1

9

I"ve read through other articles. My firefox and sync are up to date. I have bookmarks checked. I use two firefox on two different microsoft PCs. I tried changing my … (ulteriori informazioni)

I"ve read through other articles. My firefox and sync are up to date. I have bookmarks checked. I use two firefox on two different microsoft PCs. I tried changing my options in sync to see if the chances would show up in firefox on my other computer. They did, so I have that much right. I tried turning off bookmarks in the sync, syncing, then clicking the box and syncing again. I want to say it can't be me, but of course it has to be or everyone would be having the same problem.

5

1

12

After updating to Firefox 70, many websites that were previously working do not work when I navigate to them. However, if I clear the cookies related to that site, then t… (ulteriori informazioni)

After updating to Firefox 70, many websites that were previously working do not work when I navigate to them. However, if I clear the cookies related to that site, then the website works normally again. I've been having to do this for many websites and it's getting tedious. Furthermore, I've had to do this multiple times to the same sites after having cleared cookies previously. For these repeat non-functionality incidents, they come up after reopening the browser, but not every time the browser is quit.