Firefox 技術支援討論區

Concurrent with the most recent automatic windows update (may or may not be the problem), Firefox with duck-duck-go will not go to almost any site. All I get is a spinning icon or a blank page, not even any error messages. This was even true trying to go to this page until I restarted in trouble shooting mode. Until I can get Firefox working again I have been using Chrome with duck-duck-go. Note any search, i.e. 'hotels in Italy' or even 'MSN' do the same: spinning icon or blank page!! Any help would be appreciated. Also I noticed that my bookmarks were missing and there was no bookmarks drop-down on my tools line. I have run malware bytes and it showed clean, same with CCleaner. I have re-installed Firefox; no difference. Please help. and also, any way to find and replace my extensive bookmarks list? I have reduced my privacy to near zero and turned off firewalls and all limits I could find while testing for that. That did not change anything.

I've been having issues with the websites that I commonly go to no longer appear on the autosuggest list. Websites I haven't gone to for ten years appear when I type in a given sequence rather than more common ones. Website that I go to every day no longer appear.

Multiple websites suggest this sequence:

https://support.mozilla.org/en-US/kb/remove-websites-address-bar-suggestions

I follow the "clear all.." and nothing changes. How can I start anew and have FF re-learn my url history?

Hello there i use wp.pl for mailing and after i stay on the page for too long the browser lags and it starts to use a lot of memory like from 4GB to even 8GB

When choosing biometrics for 2-factor authentication, sometimes Firefox will only prompt for a physical hardware key, and Touch ID does not work. Support for built-in biometrics is inconsistent.

For reference, I am using Mac OS Sonoma 14.4.1 with an ARM processor.

I see my original question is now archived at https://support.mozilla.org/en-US/questions/1380948#question-reply I never closed it because I didn't know if my last process could really fix the issue. It didn't, not always. Over the years, there have been times when the issue would still pop up, but not as often as before (2022 and earlier).

I have a feeling that during an issue, FF is having difficulty setting up shop after starting up. Consequently, it is spending more time before it could become prepared to connect to the Net. I've come up with another "solution," which is deleting (or moving out) xulstore.json in the profile folder after exiting or before starting FF. You can create a batch command or script to execute the process.

So far, FF is connecting immediately after startup.