This site will have limited functionality while we undergo maintenance to improve your experience. If an article doesn't solve your issue and you want to ask a question, we have our support community waiting to help you at @FirefoxSupport on Twitter and/r/firefox on Reddit.

Caută ajutor

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.

Află mai multe

Acest fir de discuție a fost arhivat. Adresează o întrebare nouă dacă ai nevoie de ajutor.

Freezes on google maps

  • 4 răspunsuri
  • 0 au această problemă
  • 36 de vizualizări
  • Ultimul răspuns de lamance

more options

When I open the google maps website it functions normally for about 3-4 seconds, then firefox completely freezes not just that tab. Firefox is up to date and it happens with all addons disabled. maps seems to work fine when I access from other country domains (co.uk or .de) Also I have no problem with the site on other browsers. It does not generate a crash report.

When I open the google maps website it functions normally for about 3-4 seconds, then firefox completely freezes not just that tab. Firefox is up to date and it happens with all addons disabled. maps seems to work fine when I access from other country domains (co.uk or .de) Also I have no problem with the site on other browsers. It does not generate a crash report.

Toate răspunsurile (4)

more options

I had not tried that. I just did and maps worked fine in the private window. Not sure what that indicates, but I cleared my cookies but that did not fix it on non-private.

more options

It freezes when I have all addons/extensions/plug-ins disabled. I opened a new private window and it works fine without freezing. I thought that might mean it is cookies or something, so I reopened a normal(non-private) window and cleared all of the cookies and tried it and it still froze.

more options

Soluție aleasă

more options

I started a new profile and it's not freezing now, so I guess that fixed it. Thanks