it is a bit more complicated. It depends on what setTimout allows in its delay parameter.
> Browsers including Internet Explorer, Chrome, Safari, and Firefox store the delay as a 32-bit signed integer internally. This causes an integer overflow when using delays larger than 2,147,483,647 ms (about 24.8 days), resulting in the timeout being executed immediately.
So after the minutes would have reached 30720 minutes, it will then set the setTimeout to 61440 minutes (or 3686400000 ms) causing the setTimeout to round that number down to 0, effectively calling it immediately. So after 21 days of silence in the room except from Kenny, Kenny will IP ban itself because it will push new messages into its send queue on every event cycle, that is clamped at 4 ms.
Or the server runs out of memory due to backed up messages, whatever happens first
Is this defined by the language? Is there a defined maximum? Is it different in different browsers?
