org.apache.cordova.engine.SystemWebView.mContext leak !

[apache]

org.apache.cordova.engine.SystemWebView.mContext leak !

[janpio]

Can you please provide some more information?

[winnerliu]

use leakcanary found

[winnerliu]

@janpio

[brodybits]

Reopening for now. @winnerliu a better explanation to walk us through the issue would be really appreciated since not all of us are familiar with Leakcanary.

[pengbs]

same issue

[eugenepoplavsky]

I think I have the similar(or the same) issue.
You can reproduce it after implementing LeakCanary(link) into your "test" project(link).

Also, you can enable StrictMode(link) and check TestActivity(for example) on InstanceCountViolation

• I have this error in my app and also in your "test" project. To reproduce - reenter in the activity a few times.
  ```
  StrictMode.setVmPolicy(new StrictMode.VmPolicy.Builder()
  .detectLeakedSqlLiteObjects()
  .detectLeakedClosableObjects()
  .setClassInstanceLimit(TestActivity.class, 1)
  .penaltyLog()
  // .penaltyDeath()
  .build());

[breautek]

I'm unable to reproduce this (but could be using LeakCanary wrong...), but following their get started link, the logcat only produces org.apache.cordova.unittests D/LeakCanary: Installing AppWatcher, and nothing else. I also tried the StrictMode, but that didn't produce any output either.

Can someone confirm if this is still an issue on the current master?

[breautek]

Closing due to staleness.