Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Set `fork := true` by default, or debug memory leaks with `fork := false`

See original GitHub issue

steps

context: discussion in gitter with @hvesalai beginning here and ending here

open an SBT shell with e.g. 2GB of memory
run tests or any tasks for “a while”

problem

observe memory-pressure and eventual OOM

expectation

Memory gets properly GC’d, and the shell can run for effectively unbounded time.

notes

if fork := true is recommended for SBT repls to avoid OOMs, it should be the default
and/or: we should try to understand why large amounts of memory are leaking

sbt version: ≤1.1.1

Issue Analytics

State:
Created 6 years ago
Reactions:1
Comments:7 (5 by maintainers)

Top GitHub Comments

4reactions

OlegYchcommented, Apr 22, 2018

i’ve written a bit about debugging this https://github.com/OlegYch/blog/blob/master/sbt-fork.md

1reaction

eed3si9ncommented, Mar 4, 2018

I put “Needinfo” label here, but I don’t want it to be interpreted as “this is not a bug.” If there were no OOM in 0.13, but you and others are seeing them in sbt 1.x, there’s a potential that sbt has regressed related to testing.