A modern programming language that makes developers happier.

kotlinlang

So that concerns me. Even well tested, "pure" code could throw an OutOfMemoryError

Fatal errors are fatal to the jvm. Nothing you can do at that point

But unwinding the stack may result in a garbage collection that allows the process to continue.

No, it's just an unchecked throwable. There's nothing stopping, say, a servlet container from catching an OOME, logging it, and continuing

Tomcat, WebLogic, JBoss, they all do this

Can you link anything on this? Because they manage vms can spin a new jvm running your program.

The vm gets into a inconsistent state on OOM so even if you attempt to recover it's in an inconsistent state and weird things can happen

I can create a sample program to demonstrate

Ye, but a sample might not run into weird behaviors.

```import java.lang.StringBuilder

fun main() {
    try {
        causeOutOfMemoryError()
    } catch(e: OutOfMemoryError) {
        println("Out of Memory Error was thrown!")
    }
    println("Still alive!")
    println("Doing more stuff: " + causeOutOfMemoryError(2))
}

fun causeOutOfMemoryError(power: Int = Int.MAX_VALUE) : String {
    val s = StringBuilder("*")
    repeat(power) {
        s.append(s.toString())
    }
    return s.toString()
}```

output: ```Out of Memory Error was thrown!
Still alive!
Doing more stuff: ****```

True, but even in single-server mode containers can attempt to recover

I'll see if I can find some lecture to back up my argumentation

Right, I'm not suggesting it wouldn't cause weird behaviors - that seems self evident. It's just that an OOME isn't automatically fatal in JVM land.