Skip to content
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

Resource Leak Checker consuming excessive memory for compilation unit #6435

Open
msridhar opened this issue Jan 31, 2024 · 0 comments
Open
Assignees

Comments

@msridhar
Copy link
Contributor

Test case:
hive_parse_test.zip

To reproduce, unzip, and modify compile.sh so that CF_ROOT points to your local Checker Framework repo. Then run ./compile.sh. The checker exhausts 16GB of RAM analyzing HiveParser.java. It's a large (~30k lines) source file generated by ANTLR I think. But still, 16GB of heap for one file is a lot. Even just running the Tainting Checker on this class needs about 8GB of heap. The RLC is hurt by needing to run the MustCallChecker as a sub checker and keep its state in memory. Doing some memory profiling, it seems a significant amount of memory is consumed by the caching of flow analysis results in the org.checkerframework.framework.type.GenericAnnotatedTypeFactory#flowResult field.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant