Hi Gergely,
We use the latest versions (MOE SDK and moe-gradle 1.3.9) and also tested multiple older versions with the same result.
I think the easiest way to reproduce the described problem is your example “Taxi”.
Profile this application on a real iOS device and look at the memory usage while navigating forward and backward (go in the map view and back navigate back).
You should see a constantly increasing memory, although you expect a big memory release on the back step.
The constantly increasing memory in combination with the high memory usage (~ 600MB on application start) brings the application quickly to its memory limit.
I can’t send you a small test project, because I’m currently in vacation and I have a bad internet connection. I’ll ask some co-workers, but don’t expect a quick response - sorry for that.
It would be very interesting to know what exactly cases the huge memory usage on the application start. Is it the JVM itself? (I refer to this High RAM Usage in MOE - the user compares MOE directly with RoboVM (total RAM usage ~7MB))
Best regards,
Jucl