OOMKill is hidden during docker-based next build, build appears successful but isn't. about next.js HOT 3 OPEN

I'm about to open an MR with a proposed fix for this.

Scratch that. I realised that process.on('exit' gets called for all exits, not just SIGKILLs. The code that gets passed to this function is 0 when an OOMKill happens, which has me stumped.

from next.js.

Hi, any updates?
I did some research online but i couldn't find out a standard way to intercept the heap out of bound exception.

The best i came up with is a file based approach, like the following

process.on("exit", (code)=>{
        // if server directory is missing inside the build folder assume something went wrong
        if (code === 0 && !_fs.existsSync(path.resolve('.next/server/'))) {
            process.exit(1);
        }

        process.exit(code); 
    })

Still i don't know if this approach cover all the cases, i'd rather wait for a maintainer feedback.
And even though this seems to work for my case, i don't know if performing file system operations while your process is running out of heap memory is a good idea .

Also, the fact that node is killing its process with a 0 code might be more a nodejs related issue rather than a nextjs related one.

from next.js.

Thanks for your eyes @deh-code! As you might notice from my closed MR I originally thought I'd solved it with just a process.on("exit... before I realised that it also fires on success. Your twist would likely work for this specific example (although a 137 exit code might be more accurate if we're assuming this can only happen on SIGKILL) but I find that I'm still left thinking that surely, surely this must be accounted for with a language construct I don't know about. Or something somewhere is catching and disguising the error.

To that end maybe another example with just a basic node program getting OOMed and hiding the exit code in the same way would be useful.

As a (rubbish) workaround, I'm just checking for existence of this path after I do a next build in my Dockerfile at the moment

from next.js.