Potential memory leak in SoloEnhanced

[GoogleCodeExporter]

What steps will reproduce the problem?
1. Install LeakCanary into the build
2. Start the instrumentation test (in my case, this is with Calabash for Android
3. Have the test pause for at least 30 seconds (to give LeakCanary time to 
analyze the heap dump)

What is the expected output? What do you see instead?
Leak Canary detects a leak:

LoginActivity has leaked:
In local.myapp:1.0:1.
* local.myapp.activity.LoginActivity has leaked:
* GC ROOT static sh.calaba.instrumentationbackend.InstrumentationBackend.solo
* references com.robotium.solo.SoloEnhanced.activityUtils
* references com.robotium.solo.ActivityUtils.activity
* leaks local.myapp.activity.LoginActivity instance

* Reference Key: 8e4b95da-43fb-4af5-8ac0-9dc9b7118036
* Device: samsung samsung SM-G900H k3gxx
* Android Version: 4.4.2 API: 19
* Durations: watch=5134ms, gc=218ms, heap dump=1275ms, analysis=23376ms

What version of the product are you using? On what operating system?
Calabash 0.5.8, which uses robotium-solo-4.3.1.jar
on Mac OS X 10.10 (Yosemite)

Please provide any additional information below.

The original issue was reported to LeakCanary at 
https://github.com/square/leakcanary/issues/93#issuecomment-102206755
the maintainer believes this to be a "real bug"

Original issue reported on code.google.com by jhans...@meetme.com on 15 May 2015 at 3:56

[GoogleCodeExporter]

Sorry, "SoloEnhanced" is wrong, that's the Calabash extension of Solo (in order 
to override visibility of some fields) 

Original comment by jhans...@meetme.com on 15 May 2015 at 3:57

[GoogleCodeExporter]

Thanks for reporting this. Calabash is using an old version of Robotium. Do you 
also get this when trying the latest version of Robotium?

Original comment by renasr...@gmail.com on 16 May 2015 at 9:04

[GoogleCodeExporter]

Will open up if more information is given

Original comment by renasr...@gmail.com on 26 May 2015 at 11:16

• Changed state: Invalid