-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[Examples/clay-official-website] nicbarker.com/clay crashes in debug mode in Chrome & Edge #217
Comments
Can you be a little more specific with how one would reproduce this? |
It is really simple.
For me it takes like 10-60 Seconds for this to happen. It happens always eventually. |
I managed to reproduce it here, but it's not clear what is causing the issue. Differently than @JannesN, moving the mouse on the website randomly for minutes didn't trigger the issue here. Instead, I saw it twice, after following the steps above, changing tabs and then returning to the Clay website page, It doesn't seem to be consistent though, as I couldn't reliably reproduce it again after these 2 instances. I'm using Chrome Version 131.0.6778.266 (Official Build) (64-bit) |
I am unable to reproduce the crash with either method on Edge 132.0.2957.115 (Official build) (64-bit). |
Hello @JannesN, would you be able to include your OS details & browser version numbers? |
Hey!
I noticed your demo on your website actually crashes when going into debug mode and moving the cursor randomly over the debug UI for a while.
I tried this 3 times now and it crashed every time.
I was able to replicate the behaviour in Chrome and in Edge.
Error code: STATUS_ACCESS_VIOLATION
The text was updated successfully, but these errors were encountered: