[Bug] Chrome flickering when using Google Maps vector map with custom map style #9261
Open
Description
Description
Hi,
I have a quite big flickering problem in Google Chrome when using DeckGLOverlay/GoogleMapsOverlay (using a Google Maps Vector map with a custom style) and running this example:
https://deck.gl/docs/api-reference/google-maps/google-maps-overlay
When I resize the browser window (or a div containing a map) it is a constant flicker until I stop resizing. This is not a problem in Firefox.
Please see steps to reproduce for more details
Thanks a lot for a great project.
Best regards,
Flavors
- Script tagReactPython/Jupyter notebookMapboxOverlayGoogleMapsOverlayCartoLayerArcGIS
Expected Behavior
I expect no flickering on the Google map in Chrome when resizing the window when running:
https://deck.gl/docs/api-reference/google-maps/google-maps-overlay
Steps to Reproduce
Steps to reproduce:
- Create a google map id, and choose "Raster" as the map type.
- Create a custom map style (choose different colors) and associate the style with the map (under "Map styles", in the cloud)
- Run this example code:
https://deck.gl/docs/api-reference/google-maps/google-maps-overlay - Resize the browser window (drag the window edge) and observe that there is no flicker.
- This works well in Chrome and firefox.
- Change map type to "Vector" (and choose Tilt and Rotation).
- Wait a minute for the changes to take effect.
- Resize the browser window again. Now a very annoying flicker happens in Chrome during the resize. It still works in Firefox however!?
Environment
- Framework version: "@deck.gl/core": "^9.0.35"
- Browser: Version 131.0.6778.71 (Official version) (64 bit)
- OS: Windows 10
Logs
No response
Activity
telriot commentedon Dec 2, 2024
Having the same issue, but not on all machines.
The problem arises with Chrome 131.0.6778.85 on Mac 15.1.1.
Deck gl is at version 9.0.35.
Fabioni commentedon Jan 6, 2025
I have the same problem.
It only happens for non-interleaved deckgl layers. The interleaved once act fine. So it is probably because of the resizing of the deckgl canvas.