Clay main page appears to have a crash bug in debug UI.

[rygo6]

I'm replicating this on both of my Windows 11 PCs with the latest Microsoft Edge.

If I go to: https://www.nicbarker.com/clay

Then press 'd' to open the debug UI.

Then scroll up and down the debug UI rapidly, move my mouse cursor up and down it rapidly, clicking rapidly, and opening/closing a bunch of the foldouts rapidly. Eventually I will get a hard tab crash STATUS_ACCESS_VIOLATION.

At most it takes maybe 2 minutes of doing this to get the crash. Usually will happen in less than minute.

This DOES happen from just regular usage too. Which is why I bring it up, there does seem to be this occasional hard crash for some reason. You can induce it by doing this rapid moving/clicking over the debug menu.

Firefox does not appear to do this.

However, Edge and also Brave on two different Win 11 PCs do this. So, it is something specific to chrome.

Hoping you (or anyone) can fix or has some ideas because I don't even know where to start debugging some hard crash like this. I assume it'd have to be in WASM somewhere? But I don't know. Checking the 'Pause on Caught/Uncaught Exceptions' in Chrome Developer tools doesn't catch anything either. It hard crashes the tab with a STATUS_ACCESS_VIOLATION.

Also want to add. Amazing project. I'm hoping to make use of it, but this potential crash bug embedded deep in it is making me hesitant, so hoping can sort it out.

[Dentorol]

I think you can reproduce the crash even faster by using the page zoom in/out feature in your browser. https://www.youtube.com/watch?v=ra--Qo9nNTE

[cedric-h]

Debug UI is crashing quite regularly for me on https://nicbarker.com/clay

Using the DuckDuckGo Browser on Windows 11

Doesn't seem to crash in Chrome

[mundusnine]

@nicbarker This apparently has nothing to do with the debugUI, It's a too much branching issue caused by the Chrome code optimizer TurboFan...