Ova tema je arhivirana. Pitajte drugo pitanje ako vam je potrebna pomoć.
Google Maps Crashes
Firefox just upgraded to 80.0.1 . . . on Mac OS High Sierra . . .
- 1 Open new browser window
- 2 Go to : http://www.Google.com/maps/
- 3 paste or key an address into the "Where?" field, and
- 4 BOOM Firefox immediately closes the Google window.
On a Macbook Pro, running Mac OS High Sierra, 10.13.6 FireFox version 75.0 works perfectly, and Google Maps works perfectly.
(Except for the annoying notices to upgrade, which is what was done, finally got tired of getting the upgrade notice so she upgraded and BOOM Firefox doesn't work on Google Maps. So now she's using Safari for Google Maps)
Tip : If the upgrade doesn't work, then don't send the upgrade notices!
All Replies (2)
I have not noticed this problem on Windows.
Does it make any difference if you try a full URL instead of searching through the page? For example: https://www.google.com/maps/place/Golden+Gate+Bridge+Welcome+Centeremail@example.com,-122.4827183,14z/data=!4m12!1m6!3m5!1s0x808586deffffffc3:0xcded139783705509!2sGolden+Gate+Bridge!8m2!3d37.8199286!4d-122.4782551!3m4!1s0x0:0xfac9601f983db5bd!8m2!3d37.8077878!4d-122.4748403
If a site is generally known to work in Firefox, these are standard suggestions to try when it stops working normally:
Double-check content blockers: Firefox's Tracking Protection feature, and extensions that counter ads and tracking, may break websites that embed third party content (meaning, from a secondary server).
(A) The shield icon toward the left end of the address bar usually turns a bit purplish when content is blocked. Click the icon to learn more or make an exception. See: Enhanced Tracking Protection in Firefox for desktop.
(B) Extensions such as Adblock Plus, Blur, Disconnect, DuckDuckGo Privacy Essentials, Ghostery, NoScript, Privacy Badger, uBlock Origin or uMatrix usually provide a toolbar button to manage blocked content in a page. There may or may not be a number on the icon indicating the number of blocked items; you sometimes need to click the button to see what's going on and test whether you need to make an exception for this site.
Cache and Cookies: When you have a problem with one particular site, a good "first thing to try" is clearing your Firefox cache and deleting your saved cookies for the site.
(1) Clear Firefox's Cache
If you have a large hard drive, this might take a few minutes.
(2) Remove the site's cookies (save any pending work first). While viewing a page on the site, click the lock icon at the left end of the address bar. After a moment, a "Clear Cookies and Site Data" button should appear at the bottom. Go ahead and click that.
In the dialog that opens, you will see one or more matches to the current address so you can remove the site's cookies individually without affecting other sites.
Then try reloading the page. Does that help?
Testing in Firefox's Safe Mode: In its Safe Mode, Firefox temporarily deactivates extensions, hardware acceleration, and some other advanced features to help you assess whether these are causing the problem.
If Firefox is running: You can restart Firefox in Safe Mode using either:
- "3-bar" menu button > "?" Help > Restart with Add-ons Disabled
- (menu bar) Help menu > Restart with Add-ons Disabled
and OK the restart. A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
If Firefox is not running: Hold down the option/alt key when starting Firefox. (On Windows, hold down the Shift key instead of the option/alt key.) A small dialog should appear. Click "Start in Safe Mode" (not Refresh).
hi showker1, since you seem to be able to consistently reproduce the problem, would you be willing to run the tool from https://mozilla.github.io/mozregression/ to get us en exact regression range of when this issue was introduced? this would make it much more easy and quick for developers to fix any newly introduced bugs...