typetools / typetools/checker-framework
False positive in Resource Leak Checker
Open
Nobody has claimed this yet.
ResourceLeakChecker
- Dominant language
- Java
- Stars
- 1.1k
- Forks
- 440
- Avg merge
- 1d 12h
- Merged PRs (30d)
- 134
Description
Test is here:
I believe the RLC should be able to analyze the different paths separately and not report a warning here.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with checker/tests/resourceleak/MustCallAliasNormalExit.java at lines 60–71 and reproduce the Resource Leak Checker warning for the reported paths. Trace the checker behavior for that test and verify that separate path analysis no longer reports a false positive when the issue is fixed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100