jumbopilot

Any updates on this? I think MapBox V10 should be ready for SwiftUI soon to keep state-of-the-art.

The required code change to resolve the issue is: `let factor = height / abs(CGFloat(max - min))` instead of `let factor = height / CGFloat(abs(max) - abs(min))` in draw... functions...

Hi guys, I do experience pretty same resource consumption issue with V10.6.0 (also since I've migrated from V6) on iOS 15/16. But I suspect it to be partly already present...

@ZiZasaurus I do confirm the memory consumption and especially the memory release has been improved with v10.10. Record of Mapbox's memory consumption over time while repeatedly instantiating/dismissing a second mao...

Any updates about the memory release at view dismiss? Is there any memory releaseing to be conducted in my Mapbox integrating module? I'm not taking care of releasing any instances...

Tested with Mapbox V11: this issue is no more reproducible with V11. @OdNairy: Great, thank you!