-
Notifications
You must be signed in to change notification settings - Fork 560
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
DartPad shows white screen with WebAssembly errors in Chrome and Edge #3051
Comments
I also posted aquestion on StackOverflow regarding the issue: https://stackoverflow.com/questions/78948694/dartpad-shows-white-screen-with-webassembly-errors-in-chrome-and-edge |
Similar issue in Opera version: 114.0.5282.185 |
I'm also facing the same issue on both Edge v131.0.2903.112 (Official build) (64-bit) and Google Chrome v131.0.6778.205 (Official Build) (64-bit) browsers with the latest version. Also failing to browse embedded DartPad blocks on Flutter Dart API Docs Troubleshooting DartPad also won't help. Screenshots:Any updates from Dart team on how to resolve or fix this? |
This exact signature mismatch issue was driving me crazy on Arc, so I spent some time digging into and resetting every setting imaginable. Turns out, I had graphics acceleration disabled in chrome://settings/system which completely borked Dartpad. Hopefully enabling this and allowing third party cookies / redirects / popups (and all the other usual jazz) will help! If this alone is causing issues, you can always reset your browser settings to default, enable graphics acceleration (if needed), then give it another go 💪 |
What happened?
4 days ago, I accessed DartPad using Google Chrome, the screen was completely white.
Steps to reproduce problem
When I tried to reload again, I decided to see what was goign on using the dev tools. And I found this:
I checked the official site and ensured I’m using the latest version of Chrome:
Despite updating and restarting Chrome, the problem persists.
Here are the steps I’ve taken:
What could be the main causes? Any answers would be appreciated.
The text was updated successfully, but these errors were encountered: