当サイトはユーザー体験を改善するためのメンテナンスを実施中に機能が制限される予定です。記事を読んでもあなたの問題が解決せず質問をしたい場合は、Twitter の @FirefoxSupport、Reddit の /r/firefox で、サポートコミュニティが皆さんを助けようと待機しています。

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.

詳しく学ぶ

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

Allow Location Access completely freezes up Firefox 65.0.2

  • 3 件の返信
  • 1 人がこの問題に困っています
  • 12 回表示
  • 最後の返信者: FredMcD

more options

Firefox completely freezes up whenever I visit a page that uses geolocation services and I Allow Location Access. An example URL is:

https://www.guitarcenter.com/Used/Fender/Vintage-Reissue-1959-Bassman-LTD-4x10-Tube-Guitar-Combo-Amp.gc

Another example is FedEx.com.

I've tried troubleshooting this by running Firefox in Safe Mode but that does not help. The only way I can get those pages to work again without freezing up Firefox is to clear out or disallow location permissions.

I noticed that version 65.0.2 supposedly fixed a bug related to geolocation services affecting Windows users. Well, for me at least, this bug fix has introduced a bug that I didn't have before.

How can I get this looked into and fixed?

Firefox completely freezes up whenever I visit a page that uses geolocation services and I Allow Location Access. An example URL is: https://www.guitarcenter.com/Used/Fender/Vintage-Reissue-1959-Bassman-LTD-4x10-Tube-Guitar-Combo-Amp.gc Another example is FedEx.com. I've tried troubleshooting this by running Firefox in Safe Mode but that does not help. The only way I can get those pages to work again without freezing up Firefox is to clear out or disallow location permissions. I noticed that version 65.0.2 supposedly fixed a bug related to geolocation services affecting Windows users. Well, for me at least, this bug fix has introduced a bug that I didn't have before. How can I get this looked into and fixed?

すべての返信 (3)

more options

この投稿は FredMcD により に変更されました

more options

I can't easily tell by looking at these lists if this bug has been reported and is being addressed. They are very developer oriented (as opposed to user oriented).

more options

Sorry, I posted those for others to look over. I could not tell which bug was addressed in v65.0.2