Mobile App Heap Size Issue – Investigation & Support Request

 Eugene Bychkov  Thanks for you ack of this issue and quick reply. Here We have got some screenshots of Heap snapshot. Would request you to suggest your recommendations based on this.

Hi Chetan
The size of these heap snapshots looks 'ok' to me

You could try disabling some modules from mobile to identify which module potentially overloads your device

After that you could try further investigation according to my earlier recommendations

Hope this helps and best regards

Hi Chetan
The size of these heap snapshots looks 'ok' to me

You could try disabling some modules from mobile to identify which module potentially overloads your device

After that you could try further investigation according to my earlier recommendations

Hope this helps and best regards

Noted. Thanks for prompt reply. Will update the result.

Hi Eugene Bychkov We have checked all the scenarios. We found that we have very  Complex & Heavy UI Frameworks. We also found that there is Heap size increase on locatoin.reload() we have used in our customization.

So we need help on following,

1. Is there any kind of limitation on customizations? like memory size etc.

2. Is there any alternate for location.reload()? which also applicable for custom filter @ run time.

1. there are no explicit limitations in Sugar Mobile SDK. Any performance limitations you encounter are caused only by limits of device/OS you are using

2. i can't help with this specific question. but I doubt any alternative would help in this case, you need to debug deeper into performance issues you have with your UI