Rainforest supports testing native mobile applications on Android using the official android emulator from Google. Using emulators instead of real physical devices provides a bunch of benefits such as being able to reproduce issues locally (hard to do if you don\u2019t have the same hardware device, but trivial if you can run the same emulator), better isolation (no need to wipe\/worry about data leaking on a real device, we can just throw the entire emulator away and make a new one), faster turnaround (we are not limited by the number of physical devices), and some nice debugging features\/functionality that the emulator supports (location spoofing, virtual camera support, etc).<\/p>\n\n\n\n
One of our customers was experiencing periodic crashes of their application when testing in our Android 10 emulator. After some initial investigation it appeared that their application was exhausting the amount of heap space available leading to a crash. We found that in the instances where their application was crashing, the log messages would show that the heap was only 16 MiB. This was quite surprising to us since our emulators have ~4 GiB of memory. It was also very odd because further investigation (i.e.\u00a0adb shell getprop dalvik.vm.heapsize<\/code>) showed that the heap size should have been\u00a0576m<\/code>. So why was the application crashing after only using 16 MiB?<\/p>\n\n\n\n