Ives van Hoorne
Ives van Hoorne
I also cannot repro this with Safari, so I think this is indeed a Chrome 138 thing
> [@stevelewis99](https://github.com/stevelewis99) Right now it displays a blank screen for me in FF as well > > > Firefox 140.0.4 , Windows OS 11 I think this error in particular...
I tried to open an issue using the chromium bug tracker in Chrome & Dia, but I'm getting an error back. I will add a response to the existing issue.
I've responded to this issue tracker just now: https://issues.chromium.org/issues/429585228.
I've spent quite some time debugging this already, but because the chrome devtools also hang when the problem happens, it's extremely hard to pinpoint. I would recommend to also respond...
Should be fixed now!
Yep, it takes 20 min to deploy. It should be live now!
I unfortunately have to reopen this issue, our websocket connections got overloaded when we enabled embeds. I've reverted the change now and we're looking into fixing the scaling issues!
Yes, could be a resolver problem. Taking a look.
Okay, I have a theory and a fix. Deploying the fix now.