Well, of course an infinite loop is gonna crash the system.
And the "Wait 1 second" action is creating thousands upon thousands of "contexts" from which execution would resume from, and all that overhead needs memory... and looks like it needs a lot of it.
Absolutely not a bug, it's something you should never do, like dividing by zero.
I actually found it while creating something that supposedly isn't in a loop, and couldn't find the reason why it kept looping.
In my work, the While condition was supposed to stop once a local variable reached under 1, which would be caused by a subtract action which was being repeated by the condition.
I have now found my issue: Just like with Repeat, the While condition does not wait for the last loop to finish. The command that basically stops the loop occurs after a delay, which means there's a lot of time for other loops to start.
Looks like there isn't any bug to see here. Thank you for reminding me of that.
Though this kind of problem means anyone can crash someone else's computer in a game, so long as there's not a lot of memory to take before the user notices and attempts closing the browser.