Node 11.0.0 freezes randomly. Possibly due to some shared resource deadlock.

[adrianhelvik]

I am posting this here so you'll be aware of the issue. I will be able to provide more details when I get back to work on Monday.

So we noticed a strange bug today. A change in one node process would freeze another. We were running Webpack (create-react-app) on one process, a Node server on another and the tests on another. At the exact instant hot reloading occurred in the frontend, the backend would inexplicably freeze. No error and ctrl-c worked like normal.

That was my cue that it probably had to do with Node 11. The backend and frontend of the application are completely separate. Reverting to version 10 solved the issue.

The tests would also randomly freeze. Ctrl-c did not exit the process, but the tests are run with jest and I assume Jest prevents normal SIGINT behaviour and that the source of the problem was the same.

So my theory is that there is some sort of deadlock that happens when Node tries to access some shared resource.

The same thing happened on my colleagues computer as well and happened very much.

• Version:
  11.0.0

• Platform:
  Will update on monday

• Subsystem:

[targos]

This is probably a duplicate of #23921
Can you try upgrading to v11.1.0 before re-running your tests?

[adrianhelvik]

That definitely looks like it could the reason. I will test it on monday.

[Trott]

That definitely looks like it could the reason. I will test it on monday.

@adrianhelvik Did you get a chance to test? Is the problem resolved?

[adrianhelvik]

Ah, I forgot to do it. Will upgrade Node today and get back to you.

[adrianhelvik]

Super stressful day at work, so I forgot it again. 😓 It sounded just like the previous bug though. I'll close this now and reopen or comment when I get around to testing it.