Increase default stack size used by launcher when .jvmopts does not specify -Xss

I’m running Bloop 1.4.0-RC1 on linux.

Step 1. bloop clean - works great, np

Step 2. bloop compile root-test - compiles everything doesn’t exit at the end. Zipkin shows that all modules are compiled successfully.

Output looks normal, like this:

> bloop compile root-test
Compiling base-util-jvm (65 Scala sources)
Compiling base-util-js (57 Scala sources)
Compiled base-util-jvm (12100ms)
...
Compiled benchmark-jvm (2953ms)
Compiling benchmark-jvm-test (1 Scala source)
Compiled benchmark-jvm-test (151ms)

and then it hangs and I have to ctrl-C to kill it.

What’s really, really bad about this is that after I ctrl-C, if I run the same command again it recompiles everything (!).

> bloop compile root-test
Compiling base-util-js (57 Scala sources)
Compiling base-util-jvm (65 Scala sources)
Compiled base-util-jvm (4013ms)
...
Deduplicating compilation of base-test from cli client 'bloop-cli' (since 6m 51.545s)
...
Compiled benchmark-jvm (2593ms)
Compiling benchmark-jvm-test (1 Scala source)
Compiled benchmark-jvm-test (116ms)

and then it’s stuck again.

[olafurpg]

I wonder if the bloop launcher should by default increase the stack size if it’s not defined in .jvmopts? It’s normal that compilation requires a deeper stack size than the default and the error is currently quite cryptic when the stack overflows.

[jvican]

Fixed by https://github.com/scalacenter/bloop/pull/1174