Search Support

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

Allow Location Access completely freezes up Firefox 65.0.2

  • 3 replies
  • 1 has this problem
  • 12 views
  • Last reply by 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?

All Replies (3)

more options

Modified by 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