Take a heap dump during Android integration tests when Out Of Memory error occurs

Question

Our tester at work can't make our app get an OOM error by testing by hand, but when we run our integration tests, after about 50 or so tests we get an OOM error and the rest of the tests don't finish.

I'd like to dump the heap when we get OOM during the integration tests. I'm using Maven, and Spoon to kick off the integration tests. I'd really like to take a look at the heap to see what's killing memory. I tried connecting monitor during the test run, but the port ddms tries to hook into is tied up.

score 1 · Accepted Answer · answered Jun 06 '13 at 06:04

1

The test infrastructure could have been hooked into the ddms port.

You could actually dump the heap from your test by calling android.os.Debug.dumpHprofData(). The test should run in the same process space as your app. Hence, it should work fine. Start taking the heap dumps in each test after the 45th test and you could probably get the heap dump that you need to analyze.

answered Jun 06 '13 at 06:04

user2331248

26
1

Well, sometimes it happens earlier. It's pretty random. I'd really like to do it when OOM occurs. – Christopher Perry Jun 06 '13 at 06:23
1

May be you can try catching the OOME by installing a UncaughtExceptionHandler. Look at (http://bigflake.com/HeapDump.java.txt) for a sample code – user2331248 Jun 06 '13 at 06:35
Great example. You just taught me something new. Thanks. – Christopher Perry Jun 06 '13 at 07:01

Take a heap dump during Android integration tests when Out Of Memory error occurs

1 Answers1