-
Notifications
You must be signed in to change notification settings - Fork 935
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
Cached resolution: OOM when compiling #1763
Comments
BTW I think lila is an interesting project to test sbt with, for it has 46 more or less lousely coupled subprojects. https://github.com/ornicar/lila/blob/master/project/Build.scala#L48-L262 |
One possible explanation for more memory usage only when cached resolution is enabled is #1760. |
@ornicar I tried to pull down lila and reproduce the OOM but I'm missing a resolver for com.github.ornicar:scalalib_2.11:5.2. Could you perhaps add the necessary resolver or instructions on how to build it into the README so I can try to reproduce? |
I had to locally publish scalalib 5.1
|
Oh and I had to do this:
and change val maxmind = "com.sanoma.cda" %% "maxmind-geoip2-scala" % "1.3.3" |
Or you can run https://github.com/ornicar/lila/blob/master/bin/build-deps.sh |
Thanks @ornicar, build-deps worked great. This is the same OOM I've been seeing in my project, I was able to reproduce it in 13.7 immediately. Let me know if there's anything I can do to help track down the issue. |
Some heap optimization during merging too. YourKit showed that mergeOrganizationArtifactReports takes up huge amount of heap.
Some heap optimization during merging too. YourKit showed that mergeOrganizationArtifactReports takes up huge amount of heap.
Some heap optimization during merging too. YourKit showed that mergeOrganizationArtifactReports takes up huge amount of heap.
Hurray! I can't wait to try it out. Did you manage to compile lila with these changes? |
This case got closed when I merged #1904, but OOM persists for lila using sbt 0.13.8-RC1. |
On a build that used to OOM on update, one graph.json file for a project was growing to 250MB. 97% of the content seemed to be caller info. Parsing the json file from the REPL alone would take many hours. After removing the caller, update for the entire update finishes within minutes.
@ornicar sbt 0.13.9-M1 is out. Could you test if cached resolution works for you? |
Not only does it work, but http://lichess.org is already running code built by 0.13.9-M1!
Thank you very much! |
4 seconds after enabling cached resolution. |
With -Xmx1G. OOM does not happen with 0.13.7 without CachedResolution
Reproduce:
The text was updated successfully, but these errors were encountered: