-
Notifications
You must be signed in to change notification settings - Fork 353
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.
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
ResourceLeakChecker infinite loop #5113
Comments
I'm sorry you are having trouble. Thanks for reporting it. It would be useful if you could provide a stack trace.
It would also be useful to know which file triggers the infinite loop. Thanks for your help with this debugging! |
@mernst here's the stack trace
|
I tried adding -Afilenames, but it doesn't display any filenames. Your documentation notes that "This does not work if you are using Maven, because with forked compilation, the maven-compiler-plugin queues up all the output and then prints it at the end.", but Im not even using forked compilation. I enabled verbose output on the compiler and the last thing it shows is |
FYI #5107 should yield a significant speedup in the Resource Leak Checker. The stack you posted is one that should be optimized by that PR. It won't solve an infinite loop, but it's possible this is a case where the RLC is just slow. |
I don't think |
here's another
@msridhar thanks Ill try that |
This case should also (hopefully) be handled by #5107 |
@delanym #5107 has landed on the main branch. Is there any chance you could try running the Resource Leak Checker with a snapshot build of Checker Framework that includes the fix? To do so, clone the repository and then run |
@msridhar thanks it finished after 14m |
Thanks for reporting back! |
On some of my larger Maven modules, when I use ResourceLeakChecker, the compiler stop outputting logs (verbose logs) and hogs CPU. After 10min on one project I cancelled it.
I can't share these modules. What else can I do to troubleshoot this?
My configuration is like #5007 (comment)
Would be nice if checker-framework had a presence on Gitter, eg https://gitter.im/typetools/checker-framework
The text was updated successfully, but these errors were encountered: