Martin Schuhfuss

> @usefulthink Hi, just for your information: there is a feature to delete a specific revision of the edit history in GitHub. Probably, you have the edit permission for this....

The thing is, this has no immediate relation to anything we are doing with the maps API. That `WebglOverlay` mentioned in the error-message isn't something we create or interact with....

As far as I am aware, this also doesn't affect applications built with this library (besides an annoying error-message in the console), am I wrong on that?

@arithtic the problem here is that nobody seems to know what those techniques are, and where they are not being handled, can you elaborate?

The thing is, we're only using the `google.maps.marker.AdvancedMarkerElement`, and there's nothing in this library that has anything to do with the `google.maps.WebGLOverlayView`. The error ocurs internally in the maps API...

@paiameya is that something that I can have a look at? There might be a different issue at play there.

Turns out, the error-message can be easily reproduced with the vanilla API. I created an Issue in the maps issue tracker about this: https://issuetracker.google.com/issues/356878392 (please +1 the issue there to...

@paiameya I'm sorry, I can't reproduce the problem you are describing. And even if, it's very unlikely I could tell you anything about it without seeing the code involved. It...

@paiameya watch out for things like unnecessary renders of the map- and marker-components, that can sometimes be really bad. Also, maybe check the two updated clustering examples ([here](https://visgl.github.io/react-google-maps/examples/marker-clustering) and [here](https://visgl.github.io/react-google-maps/examples/custom-marker-clustering))...

See https://github.com/visgl/react-google-maps/issues/419#issuecomment-2263582300 – it's an issue in the Maps API and there's nothing we can do about it on our end. Please upvote the issue in the google issue tracker...