Replies: 1 comment 2 replies
-
If your library is indiscriminately scanning the entire classpath, and storing ClassInfo objects for every class encountered, then yes, ClassGraph can consume a large amount of RAM. The fix is probably to modify the library to scan the smallest set of classes possible. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
In the spring boot 3 project, we got an OOM error which caused by the ClassGraph lib.
After searching the dependency tree, our SpringDoc lib depends on classgraph in its dependencies.
Beta Was this translation helpful? Give feedback.
All reactions