You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Resource leak checker is failing during the clean up in this PR #746
We used a ugly hacky way to make resource leak checker happy, see 56afa4e
Here is the minimal test case for it.
public class Test<S> {
public S foo() {
S s = joo(new A());
return null;
}
public S joo(A b) {
return null;
}
}
class A{}
java -jar checker/dist/checker.jar -processor resourceleak Test.java
Test.java:3: error: [required.method.not.known] The checker cannot determine the must call methods of s or any of its aliases, so it could not determine if they were called. Typically, this error indicates that you need to write an @MustCall annotation (often on an unconstrained generic type).
S s = joo(new A());
^
The type of object is: S.
Reason for going out of scope: regular method exit
1 error
Think about how to clean it up and why resource leak checker is failing by the change.
The text was updated successfully, but these errors were encountered:
Resource leak checker is failing during the clean up in this PR #746
We used a ugly hacky way to make resource leak checker happy, see 56afa4e
Here is the minimal test case for it.
Think about how to clean it up and why resource leak checker is failing by the change.
The text was updated successfully, but these errors were encountered: