IssueTracker

Forgot to mention - this affects Google maps javascript API version 3.32

Thanks for reporting this issue. We verified it and we'll keep tracking it. Please note that at this point we cannot give you any information on if and when this will be investigated. You can star this task to receive further updates.

Any update on this? we are now forced to 3.32 and its causing all kinds of issues in the libraries I use.  wax.g.js https://github.com/CartoDB/wax/blob/master/dist/wax.g.js#L3523  uses a cache to store the element and then deletes it when releaseTile is called.

What seems to happen is that the map loads, getTile is called the first time, then it is called a second time and I think it releases the original call, which happens after the 2nd one, thus releasing the tiles when it shouldnt.  This happens all the time on map load and happens intermittently (more often on IE11) during zooming.

Hello, I'd like an update on this issue as well. The OverlayMapType feature is unusable for any use case requiring releaseTile. getTile being called twice, releaseTile being called on on-screen tiles, etc. This should be escalated above a P3 now that 3.32 is forced out to the world.

For those struggling with this bug, we are using a work around that does some book-keeping on the number of getTile and releaseTile calls. It's a little convoluted:

1) For each getTile call, we generate a "tile key" string based on the x,y,z tile coordinates. (e.g. "323,234,5")
2) We have a map which keeps track of a "reference count" for each key. Each call to getTile increments the reference count for the tile key.
3) The element that we return from getTile has a "data-tile-key" attribute which is set to the key for that tile
4) In getTile, if the reference count for the key is greater than one then we know this is a duplicate getTile call, so we just return an empty div with the "data-tile-key" attribute
5) In releaseTile, the first thing we do is read the "data-tile-key" attribute from the node being released and decrement the reference count for that key. If the reference count is zero, then we know that the tile is really going offscreen and so we release any resources associated with that tile.

Works for us, but of course this is a just a big hack to work around a bug that shouldn't be there in the first place.