為了改善您的使用體驗,本網站正在進行維護,部分功能暫時無法使用。若本站的文件無法解決您的問題,想要向社群發問的話,請到 Twitter 上的 @FirefoxSupport 或 Reddit 上的 /r/firefox 發問,我們的社群成員將很快會回覆您的疑問。

搜尋 Mozilla 技術支援網站

防止技術支援詐騙。我們絕對不會要求您撥打電話或發送簡訊,或是提供個人資訊。請用「回報濫用」功能回報可疑的行為。

了解更多

Firefox was crashing often, now it does it all the time after updating to 113.0

  • 6 回覆
  • 0 有這個問題
  • 1 次檢視
  • 最近回覆由 lfox1

more options

Some pages were crashing before, now that I have updated to 113, happens on almost any page. Same problem in troubleshooting mode, so not an extension, plug-in, etc. Attached troubleshooting info.

Some pages were crashing before, now that I have updated to 113, happens on almost any page. Same problem in troubleshooting mode, so not an extension, plug-in, etc. Attached troubleshooting info.

被選擇的解決方法

uninstall your browser and download it back again might solve the problem

從原來的回覆中察看解決方案 👍 1

所有回覆 (6)

more options

clear cache and check if your drivers are up to date

more options

Thanks. Same result.

more options

選擇的解決方法

uninstall your browser and download it back again might solve the problem

more options

maybe browser using too much ram and its crashing it self

more options

Thank you for sharing your crash report IDs. Many are several weeks old, but the ones for Firefox 113.0 are all similar -- the all have the same crash signature -- in a way that the previous reports are not similar:

Signature: WebPGetFeaturesInternal

Latest reports: https://crash-stats.mozilla.org/signature/?product=Firefox&signature=WebPGetFeaturesInternal

I think about half of those could be yours. Unfortunately, there isn't much analysis available yet for us to go on.

Does it make sense that your Firefox is trying to load/decode a WebP-format image at startup, either because it is part of your home page or a page being automatically restored from a previous session?

more options

lazizakhmedov1014 said

uninstall your browser and download it back again might solve the problem

Sigh. Troubleshooting 102... this worked. Thanks for the assist. Obviously should have done this after clearing cache, etc.