John Happy
John Happy
Has anyone found a solution/alternative to setData?
Even after waiting for prior setData rendering to complete and the map to idle, memory isn't freed and subsequent setData calls continue to crash the browser though. Am I missing...
Can confirm I'm also observing this behavior on Firefox, Chrome, and Safari (but not Edge). Even running setData just several times per second with minimal changes is enough to quickly...
Is there any alternative way to update a source's FeatureCollection without setData while this is being looked into? Or some replacement for mapbox that won't require too much refactoring?