-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Memory Leaks when using QuarkusTestProfile #12498
Comments
Fixes quarkusio#12498
It appears that groovy is going some stuff with soft references that prevent the ClassLoader being collected. Further work should be done at some point to figure out what is wrong, but for now we can just make it parent first. Fixes quarkusio#12498
Also moves a misplaced fix for quarkusio#12498 to the correct spot. Fixes quarkusio#16762
Also moves a misplaced fix for quarkusio#12498 to the correct spot. Fixes quarkusio#16762 Fixes quarkusio#16755
What's the state of this issue? We are hitting the same with 1.13.1.Final, openjdk version 11.0.10. We are using two simple test profiles, each one changing a single property.
|
Does that same error occur with If so, can you please open a new issue and attach the project you are using to reproduce the problem? |
i'm also facing similar issue , i have below logs While running test case separately there is no issue its running fine , but running as a whole all test cases , its failing at same test case https://gist.github.com/saravana2906/bc76f162880507b6186ca5e56bdb5f91 Quarkus version using: |
@saravana2906 can you please attach a sample project that exhibits the problematic behavior? |
@geoand i will try to separate the code and reproduce this issue . Is there anything we can find from logs. |
Thanks |
Having the same problem. Do you have any workaround for this? Do you still need a reproducer? |
Describe the bug
I have a project with something like 10 test classes that each use a different Test Profile. There seems to be some kind of memory leak where something is not cleaned up correctly when a quarkus application was stopped after each of these classes.I am not sure if I am doing anything wrong or uncommon, or whether is actually an error in Quarkus.
Expected behavior
I can run all tests.
Actual behavior
I run the tests but the memory usage is rising which eventually leads to
OutOfMemoryError
s.To Reproduce
I created a small example project where I reproduced my problem with 10 Test classes and a limited heap space of
64m
. The VM only runs 2 tests and then crashes due to a lack of free heap space. When I limit to128m
it runs around 7 tests before it crashes.See this repository that also contains a log output: https://github.com/dhenneke/test-profile-memory-leak
Log output as copied from the repository
Environment (please complete the following information):
I got the problem on my Windows Machine but decided to startup a Ubuntu Cloud-VM to check it also on a unix-system.
uname -a
orver
:Linux ubuntu-s-1vcpu-1gb-fra1-01 5.4.0-45-generic #49-Ubuntu SMP Wed Aug 26 13:38:52 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
java -version
:GraalVM version (if different from Java):1.8.1
+ the latest master snapshot (*/quarkus-bom/999-SNAPSHOT/quarkus-bom-999-20201003.021434-455.pom
)mvnw --version
orgradlew --version
): Happens on both Maven and GradleThe text was updated successfully, but these errors were encountered: