Mozilla Relay is experiencing issues with call and text delivery. We’re working on a fix. Check Mozilla Status for updates.

Funkcionalnosć tutoho sydła so přez wothladowanske dźěła wobmjezuje, kotrež maja waše dožiwjenje polěpšić. Jeli nastawk waš problem njerozrisuje a chceće prašenje stajić, wobroćće so na naše zhromodźenstwo pomocy, kotrež na to čaka, wam na @FirefoxSupport na Twitter a /r/firefox na Reddit pomhać.

Avatar for Username

Pomoc přepytać

Hladajće so wobšudstwa pomocy. Njenamołwimy was ženje, telefonowe čisło zawołać, SMS pósłać abo wosobinske informacije přeradźić. Prošu zdźělće podhladnu aktiwitu z pomocu nastajenja „Znjewužiwanje zdźělić“.

Dalše informacije

Tuta nitka je so archiwowała. Prošu stajće nowe prašenje, jeli pomoc trjebaće.

Google Maps display turns black.

  • 2 wotmołwje
  • 2 matej tutón problem
  • 4 napohlady
  • Poslednja wotmołwa wot jcholcomb

jcholcomb
jcholcomb
more options

This has been a problem in the past, about a year ago, and had been fixed, but it is happening again, so I thought I would restart the thread on it. After initially displaying Google Maps correctly, the display turns completely black, except for the navigation buttons and map data copyright information. Using the suggestions in this article, I found disabling the hardware acceleration in Firefox, and/or clearing the cache, cures the issue for now. https://support.mozilla.org/en-US/questions/995980. Note that I have had the same graphics card in this PC since before this problem started, and had no trouble with Firefox. The problem started with Firefox 40.0, and it just updated to 40.0.2, but the problem is still there. I am leaving the hardware acceleration disabled for now, but will try it again after future updates.

This has been a problem in the past, about a year ago, and had been fixed, but it is happening again, so I thought I would restart the thread on it. After initially displaying Google Maps correctly, the display turns completely black, except for the navigation buttons and map data copyright information. Using the suggestions in this article, I found disabling the hardware acceleration in Firefox, and/or clearing the cache, cures the issue for now. https://support.mozilla.org/en-US/questions/995980. Note that I have had the same graphics card in this PC since before this problem started, and had no trouble with Firefox. The problem started with Firefox 40.0, and it just updated to 40.0.2, but the problem is still there. I am leaving the hardware acceleration disabled for now, but will try it again after future updates.

Wšě wotmołwy (2)

philipp
philipp
  • Moderator
more options

hello, this problem will most likely "cure" itself on its own within the next hours. it's caused by mozilla temporarily putting your graphics card/driver combination on a blocklist to prohibit it using some elements of hardware acceleration (because it as crashing an unusual amount of crashes). this decision has been reverted now and will filter through to all installation automatically, since the blocklist information is updated once a day.

jcholcomb
jcholcomb Prašer
more options

philipp said

hello, this problem will most likely "cure" itself on its own within the next hours. it's caused by mozilla temporarily putting your graphics card/driver combination on a blocklist to prohibit it using some elements of hardware acceleration (because it as crashing an unusual amount of crashes). this decision has been reverted now and will filter through to all installation automatically, since the blocklist information is updated once a day.

OK, thanks for the quick response. I will try again later. To be honest, I am not seeing much difference in how fast or smooth Firefox works with hardware acceleration on or off. Perhaps, as I use it more without it, I will notice more of an improvement later.