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

Firefox Google Maps goes black after switching to multi-monitor

  • 5 ŋuɖoɖowo
  • 0 masɔmasɔ sia le wosi
  • 19 views
  • Nuɖoɖo mlɔetɔ wimmer1

more options

The problem that Google Maps goes black after a few seconds was reported here a couple of times.

I have a variation of the problem in that it appears only when I connect my laptop (Lenovo P15 with Nvidia Quadro RTX 3000) to an external monitor. After connecting, the only way to get Google Maps to work again is to close Firefox and restart it. Closing and reopening the tab or force-reloading is not sufficient.

The problem that Google Maps goes black after a few seconds was reported here a couple of times. I have a variation of the problem in that it appears only when I connect my laptop (Lenovo P15 with Nvidia Quadro RTX 3000) to an external monitor. After connecting, the only way to get Google Maps to work again is to close Firefox and restart it. Closing and reopening the tab or force-reloading is not sufficient.

All Replies (5)

more options

That sounds like the Switch Display mode isn't working correctly or recognizing the monitor switching modes. Did you check to insure the Display out is working correctly when switching modes.

more options

I don't know what you mean "the Display out is working correctly"? Everything is working correctly, just Google Maps in Firefox briefly shows the map (you can even zoom in), but when all UI elements are rendered, the map fades to black. You can still interact but everything is black...

more options

The only problem is another person whom as ext. Monitor connect to similar laptop will have to test to find out if they get the same issue or not. So you might have to wait to see when someone replies back if it affected them or not. I don't have that setup as my laptop is by itself and desktop has the monitor attached to it.

more options

Are there WebGL related messages in the Web Console and on the "Help -> More Troubleshooting Information" (about:support) page  ?

more options

The webconsole shows nothing specific to this behavior. I get the following errors, but they appear regardless of whether the page turns blank or not (after a browser restart):

`WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. rs=ACT90oGPBCwdks9W3hABgomlz_GlPgU-SA:2180:358 WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WebGL warning: texSubImage: Texture has not been initialized prior to a partial upload, forcing the browser to clear it. This may be slow. WebGL warning: texSubImage: Tex image TEXTURE_2D level 0 is incurring lazy initialization. WEBGL_debug_renderer_info is deprecated in Firefox and will be removed. Please use RENDERER. ´