Why do you think an exception should be thrown?  The expression "i+5" should be evaluated as expected and i isn't changed, so this is an infinite loop and chrome probably crashes because it runs out of memory pushing 0 to the array.

Because it's nearly impossible to find such a loop in a large codebase if the browser crashes. Therefore an exception would be much appreciated. However, this is probably rather a feature request and not a bug.

The NextAction date has arrived: 2018-06-28

Seems to be a feature request for devtools. Although I don't think this is entirely feasible currently.

Thanks for the request.  I don't think it's feasible to break/throw on any long-running piece of code.  In this case, perhaps you want to do 'Sources' > 'Pause script execution', stop all execution, and investigate?

When I did the repro locally, I expected to get our 'Paused before potential out-of-memory crash', but the tab crashed instead.
kozy@, do you know when our OOM checker is supposed to break?

Unfortunately we do not support all different kind of OOM since we can not instrument all of them.
In this case I suggest to pause execution if page is unresponsible, then you can kill current loop by long click on resume button and click terminate execution: https://twitter.com/ak_239/status/979767841573359618