You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@cordova.apache.org by GitBox <gi...@apache.org> on 2019/11/06 09:31:46 UTC
[GitHub] [cordova-android] YauhenPaplauski commented on issue #529:
org.apache.cordova.engine.SystemWebView.mContext leak !
YauhenPaplauski commented on issue #529: org.apache.cordova.engine.SystemWebView.mContext leak !
URL: https://github.com/apache/cordova-android/issues/529#issuecomment-550225362
I think I have the similar(or the same) issue.
You can reproduce it after implementing LeakCanary([link](https://square.github.io/leakcanary/getting_started/)) into your "test" project([link](https://github.com/apache/cordova-android/tree/master/test)).
Also, you can enable StrictMode([link](https://developer.android.com/reference/android/os/StrictMode)) 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());
```
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
users@infra.apache.org
With regards,
Apache Git Services
---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@cordova.apache.org
For additional commands, e-mail: commits-help@cordova.apache.org