Fixed
Status Update
Comments
th...@google.com <th...@google.com> #2
I do have found that sometimes, under some "isolated non-obvious" circumstances, some memory is actually freed (see attached image). But I agree with this post, because in general, it seems like no memory is ever freed by Google Maps SDK.
To me, the most important problem here is that the map does not free memory nor even when memory warnings are received, so you can have your app performing really bad at a given moment just because there are tiles in memory from Google Maps SDK that you actually are not seeing in your map view at that moment.
To me, the most important problem here is that the map does not free memory nor even when memory warnings are received, so you can have your app performing really bad at a given moment just because there are tiles in memory from Google Maps SDK that you actually are not seeing in your map view at that moment.
fu...@gmail.com <fu...@gmail.com> #3
yes that is it... thanks for the image. it reflects what I see.
st...@gmail.com <st...@gmail.com> #4
I think a serious problem, for old devices (3GS / 4).
ge...@gmail.com <ge...@gmail.com> #5
+1 for a config option to use the higher zoom level for retina display. Merging 4 images to a single 512*512 image is definitely doable but not the nicest solution.
Description
I don't see a way to specify a scale factor in GMSURLTileLayer and this no way to fetch retina tiles. At first I thought it might just +1 the zoom level to handle retina but this doesn't seem to be the case. Am I missing something obvious?