New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

False positive in Resource Leak Checker when type variable has a non-empty MustCall type #4837

Open

kelloggm opened this issue Jul 26, 2021 · 0 comments

Labels

False Positive (false warning or imprecision) ResourceLeakChecker

Milestone

Contributor

kelloggm commented Jul 26, 2021

The test https://github.com/typetools/checker-framework/blob/master/checker/tests/resourceleak/Issue4815.java demonstrates a false positive from the Resource Leak Checker. I don't know why this warning is issued, because the code looks safe to me. This false positive should be investigated and fixed.

This is a continuation of #4815, which reported a crash from the RLC on that test case. #4821 fixed the crash, but the false positive remains.

kelloggm added the False Positive (false warning or imprecision) label

kelloggm mentioned this issue

Resource Leak processor throws an exception when @MustCall is annotated on a Type Variable #4815

Closed

msridhar added the ResourceLeakChecker label

msridhar added this to the Medium milestone

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment