POST
|
Hi Mark, Sorry for my late answer, but I tried to analyze my problem a even more. Now I think that my problem is not that the images are not released, but there is to much RAM used by the framework. For example: My app starts and uses 80MB of RAM, than I start the map view controller and after that the app reserved nearly 200MB. When there are some images loaded from the map server by one zoomed out layer there are 220MB reserved. After zooming into detail the app reserved 240MB. That is the maximum for one layer, ok. The result for me is that one layer needs up to 40MB of RAM. So now, I want to load more than 20 layers and that seams to be impossible. But if I load an image by a normal browser based http-client, the image is only 40KB big. My conclusion is that there has to be only 20*40KB -> 800KB reserved by the map, but there are gigabytes reserved. First I thought that perhaps there are also the feature information loaded but that is not. However, my new Question is, why does every layer needs such a lot of RAM and is there a possibility to reduce the RAM usage? Next Point is that your idea, to replace the map to release everything when the map view is getting closed, does only work for some parts of the RAM usage. At all there are about 100MB left on the RAM. And if I start a new map view controller, the RAM usage is added above these 100MB. The result is that the RAM usage increases with every map view controller start and is never released. Could you reproduce that? I have forgotten to tell you that I am using the objective-c framework 100.1.0. Oliver
... View more
08-28-2017
07:55 AM
|
0
|
1
|
808
|
POST
|
Mark, thanks for your support. I'm curious to hear from you. Thanks, Oliver
... View more
08-15-2017
12:19 AM
|
0
|
1
|
808
|
POST
|
Thank you, Mark, for your answer. The memory leak exists on simulator and on the native device. As device and as simulator I tested with an iPad Air. The difference is only that the device crashes at 500MB of memory usage and the simulator is getting up to 2GB RAM. Regrettably, the service against I'm developing is a private service behind authentication. The crash only happens because of the memory leak. The memory usage of my app, especially of the map view controller, rises all the time. Even the memory is not released when the view controller is closed. So it is cumulated every time the controller opens. All in all the the loaded map images are never released from memory. That's my problem. Thanks, Oliver
... View more
08-10-2017
08:54 AM
|
0
|
1
|
808
|
POST
|
I'm integrating a lot of AGSArcGISMapImageLayers (20-30) by version 100.1.0 and now there is the problem that the loaded tiles are never released. The result is that my app crashes while zooming. Is there a possibility to release the loaded tiles by myself or is there an attribute that avoids 'caching'?
... View more
08-08-2017
02:41 AM
|
0
|
7
|
1297
|
Online Status |
Offline
|
Date Last Visited |
11-11-2020
02:24 AM
|