Memory usage of OTP-27 - OOM SIGKILL - insufficient swap space

[crownedgrouse]

Describe the bug
A same code is compiling OK with 26.2 and fails due to OOM kill (exit 137) on 27.0.1 .
This ticket is mainly to inform community of such issue.

To Reproduce
Compile a big project with only 980 Mo Swap

Expected behavior
Inform users of minimal swap partition to use 27.0 safely.

Affected versions
27.0

Additional context
Issue disappear by adding 1 Go swap but is then full up to 1.8 Go (2 swap partitions).

[jhogberg]

Thanks for your report! Unfortunately most of us are on vacation right now, we'll revisit this once we're back. :-)

[josevalim]

I am afraid this will pretty much depend on the project? As the compiler changes between Erlang/OTP versions, it may change the amount of memory it requires. Even things like making the compiler faster can change the memory profile (it can now do more, in less time, allocating more memory). Other things like concurrency will affect it too (depending on the build tool you are using). I don't think the amount of memory used by the compiler was ever a guarantee of the compiler or the build tool.

[bjorng]

Inform users of minimal swap partition to use 27.0 safely.

I don't see that this is practical. As @josevalim points out, it very much depends on the project. Therefore I will close this issue.

[frej]

Although if the compiler suddenly requires twice the amount of memory it could be worthwhile to report it. But for it to be actionable the report would have to be along the lines of "The attached module requires X of memory to compile with OTP-N, while in OTP-(N-1) it only required Y". The same applies to compilation speed.

[bjorng]

Yes, as @frej said, we are interested in actionable bug reports of regressions in compilation speed or memory consumption.