Robotium 5.2.1 OutOfMemory issues on big projects

[GoogleCodeExporter]

For large projects (300+ test) application started crashing with OOM after 
upgrading to robotium 5.2.1. This never happened before on 4.x versions.

I've investigated memory for leaking objects and looks like there are lots of 
references being kept on activities that were supposed to be closed and 
abandoned. 

Original issue reported on code.google.com by [email protected] on 31 Aug 2014 at 6:39

[GoogleCodeExporter]

Just to add more details, here's how my tearDown method looks like:

 protected void tearDown() {
        solo.assertMemoryNotLow();
        solo.getCurrentActivity().finish();
        solo.finishOpenedActivities();
        solo.finalize();
        solo = null;
        System.gc();
        Runtime.getRuntime().gc();
        super.tearDown();
}

Original comment by [email protected] on 31 Aug 2014 at 6:44

[GoogleCodeExporter]

Thanks for reporting this. It will be fixed in the next release. 

Original comment by [email protected] on 31 Aug 2014 at 7:27

• Changed state: Accepted

[GoogleCodeExporter]

Hi Renas,

I am running an automation test suite having around 500 test cases with 
robotium API 4.3.1. However I am getting out of memory after the execution of 
around 140 test cases. This is my tearDown method :

 protected void tearDown() {
        solo.getCurrentActivity().finish();
        solo.finishOpenedActivities();
        solo = null;
        System.gc();
        super.tearDown();
}

I tried with the latest API 5.2.1  as well but still got the OOM. Please let me 
know which version I should use. 

Original comment by [email protected] on 6 Nov 2014 at 6:28

[GoogleCodeExporter]

I have a 16g sd still low memory cant even dowload a g
ood game app please help 2085981614

Original comment by [email protected] on 26 Dec 2014 at 8:25

[GoogleCodeExporter]

Does anybody have an estimate for when this issue might be fixed?  As soon as a 
5.2.2 SNAPSHOT is available I would love to give it a try!

Original comment by [email protected] on 23 Jan 2015 at 5:26

[GoogleCodeExporter]

Dan and others who can help us test the fix, please email us at 
[email protected] and we'll send you our latest snapshot. Thanks.

Original comment by [email protected] on 27 Jan 2015 at 3:24

[GoogleCodeExporter]

To anyone that is experiencing this issue. Please run monkey or a similar 
stress test tool to make sure its not the app under test that is leaking 
memory. Make sure that monkey traverses all the Activities.

Original comment by [email protected] on 6 Feb 2015 at 2:35

[GoogleCodeExporter]

One of the causes for OOM in our project is missing assets matching the 
emulator screen density (i.e, only provide xhdpi and mdpi assets but running on 
hdpi emulator).  Added the right assets made OOM a lot less frequent, but still 
did not completely fix it.

Original comment by [email protected] on 8 Jul 2015 at 6:22