Jeff Lockhart

CPU profiling identifies `GoogleMap.addPolygon()` as the bottleneck adding `KmlLayer` to the map. Within this method, the bottleneck is `ArrayList.sort()`, called in a couple places by `Collections.sort()`. The long-running `KmlLayer.` can...

@barbeau I actually did pull the maps v3 branch to test and ran into [this crash](https://issuetracker.google.com/issues/132367948) again on my Pixel Slate. I'll try profiling again on my phone. I also...

I profiled with the maps v3 beta (https://github.com/googlemaps/android-maps-utils/pull/608) and actually couldn't get the KML to display on the map at all. The app hung for a few minutes with the...

@barbeau yes, with the v2 SDK it takes 10-15 seconds to add the polygons and display on the map. So this is a regression in v3. I created [a bug...

Not stale

Not stale

@JakeWharton excellent. I'll take a look at moving to a companion object. Looks like once #1131 is merged, we'll have to duplicate `actual BufferedSource` in **appleMain** and **nonAppleMain** source sets,...

@JakeWharton I took a crack at moving these extensions to the companion objects and testing in an iOS app with a KMM shared library with okio as a dependency. I...

@arkivanov yeah, it's an extension function that shadows the JVM field, documented here: https://kotlinlang.org/api/kotlinx.coroutines/kotlinx-coroutines-core/kotlinx.coroutines/-i-o.html

@OlavAa this should be fixed in #1166. I debugged and tested with your ef3_original.kmz file above.