You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

Sam Blackshear 9cf74e0ce5 [infer][backend] basic Activity leak checking ... Summary: Creating a persistent reference to an Activity leads to a nasty form of memory leaks (see http://android-developers.blogspot.com/2009/01/avoiding-memory-leaks.html, https://corner.squareup.com/2015/05/leak-canary.html). There are many ways to create a bad persistent reference to an Activity, but the most obvious one is via a static field. This diff implements a very simple form of Activity leak checking by inspecting postconditions to see if a subtype of Activity is reachable from a static field (and it reports an error if so). This is a very simple and limited form of leak checking that does not understand the Android lifecycle at all. In particular, if one creates a persistent reference to an Activity and then nulls it out in `onDestroy` (a reasonably common pattern), this approach will wrongly report a bug.		10 years ago
..
androidFramework.ml	[infer] adding is_activity method	10 years ago
androidFramework.mli	[infer] adding is_activity method	10 years ago
harness.ml	[infer][backend] basic Activity leak checking	10 years ago
harness.mli	[infer][backend] basic Activity leak checking	10 years ago
inhabit.ml	[Infer] resolving TODO's by using java_is_static	10 years ago
inhabit.mli	[whitespace] ocp-indent the code	10 years ago
stacktrace.ml	[whitespace] indent .ml files as well	10 years ago
stacktrace.mli	[whitespace] ocp-indent the code	10 years ago