Mozilla サポートの検索

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

このスレッドはアーカイブに保管されました。 必要であれば新たに質問してください。

Update on/about 21 April 2021 caused crash on quit

  • 2 件の返信
  • 0 人がこの問題に困っています
  • 19 回表示
  • 最後の返信者: 2fer

more options

I am using Mac OS x 10.15. The FireFox Update on/about 21 April 2021 caused crash on quit. I have read the two pages of Widevine plugin issues, but I do not use FireFox for viewing videos. I have no Widevine or similar plugin. Every time since the 4/21 update, when I click "Quit FireFox" It goes into a slow routine, then a pop-up asks if I want to report the crash. I have shared the data requested when I get the crash pop-up. I have used FireFox since v.3.? when it came out way back when. Obviously I liked it better when I did not have delay and crash to quit the browser.

This went on for about two years and was fixed about a week ago (Thank you!!!), now broken again with 110.0.1.

Please, any reason not to roll back to the previous version and have a smooth shutdown again?

I am using Mac OS x 10.15. The FireFox Update on/about 21 April 2021 caused crash on quit. I have read the two pages of Widevine plugin issues, but I do not use FireFox for viewing videos. I have no Widevine or similar plugin. Every time since the 4/21 update, when I click "Quit FireFox" It goes into a slow routine, then a pop-up asks if I want to report the crash. I have shared the data requested when I get the crash pop-up. I have used FireFox since v.3.? when it came out way back when. Obviously I liked it better when I did not have delay and crash to quit the browser. This went on for about two years and was fixed about a week ago (Thank you!!!), now broken again with 110.0.1. Please, any reason not to roll back to the previous version and have a smooth shutdown again?

すべての返信 (2)

more options

It is worse now, I won't even use Firefox until there is an update because now instead of pretending crash on close, it leaves 3 instances of itself anchored in my dock and superheats all the cores. Nope, not my browser anymore. I've been using it for years but it is currently unusable since the April 17 update.

more options

Since I did not know the FF v. # when I posted most recently, I have determined it was 112, though I understand why it isn't auto-detected since I won't use FF any more and had to log in on Safari.