-
Notifications
You must be signed in to change notification settings - Fork 118
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
OOM and memory leak again in gerrit #381
Comments
@laeubi : was there any change on Tycho side similar to eclipse-tycho/tycho#879 that could again cause OOM's? @sravanlakkimsetti : did we changed anything related in the aggregator poms? I don't see any tycho version change, is is still |
@mickaelistria : I see eclipse-tycho/tycho#1300 (Surefire 3.0.0.M7) was merged in Tycho some days ago. surefire update was also the root cause in eclipse-tycho/tycho#879. I assume it's same problem now. |
Yes most likely. I was expecting some improvement on that topic, but the Maven issue about the memory leak is still open, so nothing concrete happened apparently. I'm reverting that in Tycho. |
I've temporarily bumped memory to see how far we get, and we are close to 1.5 GB: If fixed Tycho is there, we should revert 660f463 |
Fixed in Tycho, so reverted the temporary workaround via #467 |
We have again OOM error reported in gerrit, see
There were no changes on master except #325, which is unlikely the root cause.
The #380 only bumps bundle version.
Search in the console for
Memory usage reported by JVM
.We see that memory constantly grows between test suites, despite the fact that we call gc and finalization.
The total memory given is 1 GB, the tests start with
22.987.912 bytes used heap
and end with multiple OOM's with this picture:So there is some memory leak now. it is either coming from some other platform changes on 4.26 or from external changes like tycho, surefire or whatever else.
This reminds me on #2 that was caused by Tycho leak: eclipse-tycho/tycho#879
Similar to Tycho bug, we have a constant memory growing with every test.
The text was updated successfully, but these errors were encountered: