-
Notifications
You must be signed in to change notification settings - Fork 186
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
Scalafix sbt causing OOM errors #1965
Comments
Maybe the jgit update broke things? |
Or it might be scalameta/scalameta#3650 though it's curious the stack trace show ScalafixCompletions and scalafix is not even being run |
I think jgit use too many memory. here is profile memory result just launch sbt in my private large repository. just launch sbtif remove
|
Yes scalacenter/sbt-scalafix#378 remove |
also jgit use many memory if repo is too many commits and/or many branch, tag. I think
see following reproduce repo |
Indeed, there is an inherent leak there, which predates sbt-scalafix 0.12.0. I am on my phone right now so I cannot check, but I am unsure how the upper bound set by In any case, feel free to open a follow-up PR 👍 |
workaround -addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.12.0")
+// TODO remove explicit "scalafix-interfaces" dependency if sbt-scalafix 0.12.1 released
+addSbtPlugin("ch.epfl.scala" % "sbt-scalafix" % "0.11.1")
+libraryDependencies += "ch.epfl.scala" % "scalafix-interfaces" % "0.12.0" |
Any plans to release new version? 👀 |
Yes! 2.13.14 is around the corner so I am holding the release a bit (to provide 2.13.14 compatibility in the testkit). Based on the current ETA, it should be last days of April. |
This started happening after the most recent release and always breaks on a stack trace:
even if no scalafix task is actually run.
Were there any changes recently that could cause it?
The text was updated successfully, but these errors were encountered: