IDOM Stalling Due to Rapid Refreshes

[Archmonger]

Originates from reactive-python/reactpy-django#22

Summary

IDOM can stall during some conditions (no longer capable of rendering new components), and the only solution is waiting it out.
This fully breaks IDOM for web development, since IDOM completely halts whenever a webpage is refreshed too quickly.

Steps to Reproduce

Rapidly refresh the client (webpage in a Chromium browser), or rapidly refresh the backend (ex. via Django Autoreload).

Analysis and Details

• Seems to be able to be replicated on any ASGI websocket
• The client can get stalled if a client side WS disconnection event doesn't occur (until WS keep-alive timeout)

OLD: Analysis and Details

• Perhaps this is related to refreshing the page in the middle of the element's first render.
• My best guess is this is some bug related to dispatch_single_view, which means it digs into IDOM Core.
• I've confirmed I can also completely break IDOM on our server used for IDOM docs examples.
• Also occurs Conreq's app store branch on Windows 10
• Somehow restarting the python interpreter does not resolve this.
• Issue automagically fixes itself after waiting 1-2 minutes. Something is timing out but I can't determine what.

[rmorshea]

I'm able to reproduce when running the docs locally. This is a pretty bad bug so it'll be top priority unless anything else comes up.

[Archmonger]

These also don't work in Brave

window.addEventListener("unload", function () {
	COMMAND_SOCKET.close();
});

window.addEventListener("unload", function () {
	try {
		COMMAND_SOCKET.close();
	} catch (error) {
		// Nothing is ever printed
		console.log(error);
		return;
	}
});

[Archmonger]

Since it's only Brave out of the Chromium bunch that has this issue, I would suspect it's something specific to Brave that we can't resolve.

[Archmonger]

GH issue for brave has been created brave/brave-browser#19080

[rmorshea]

It looks like there's a beforeunload that might work too?

[Archmonger]

Tested that as well last night, didn't change the behavior.

[Archmonger]

brave/brave-browser#19080 <- My report
brave/brave-browser#19123
brave/brave-browser#15410

Seems like similar flavors of this issue have been reported before on the Brave side. So we can safely ignore Brave's oddball behavior for now and add an unload event handler for every other browser.