Skip to content

Gradle spotless plugin using large amounts of ungcable heap in daemon when using 'ratchetFrom' #735

@itsyaboiyeah

Description

@itsyaboiyeah

In my project, if I use the ratchetFrom argument when using spotless then the gradle daemon requires 4GB more heap than without it. The size of the repo on git is 130MB. Heap analysis shows the 4GB to not be able to get collected.

I am using gradle 6.6.1, my plugin version is 5.6.1.

My OS is Windows, but this occurs on Linux also.

Sorry I can't link the repo, it is private. It is a large multi module Scala project using gradle as the build tool, we apply the spotless plugin to most of the modules, the spotless configuration looks something like so (some fields redacted)

spotless {
  ratchetFrom 'origin/master'
  scala {
    target fileTree('.') {
      include '**/*.scala'
      exclude '**/build/**'
     }
   trimTrailingWhitespace()
   endWithNewline()
   scalafmt("$scalafmt").configFile("$rootDir/.scalafmt.conf")
  }
}

No errors are emitted when running.

Sorry I have not been able to artificially replicate the problem, it does not seem to be related to the size of the repo.

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions