-
Notifications
You must be signed in to change notification settings - Fork 3.4k
The latest tag 2.0.34 is broken (fixed in main) #15539
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
Comments
We are currently looking into a few regressions due to a different change (#13006) before we tag the next release which will most likely be 3.0.0. Hopefully we can tag a new release which will include #15327 before the end of the week. I assume your concern is mostly for other users since you have determined that 2.0.34 has issues with our project and you can use 2.0.33 instead? |
Yes, that was exactly my concern, since I spent quite a while myself trying to debug the crash. Thanks for the clarification about the upcoming release. |
@K-os Meanwhile you can use |
I'll close this, since 3.0.0 is out and the problem is fixed. |
The latest tag 2.0.34 is currently seriously broken for my project due to #15327. The problematic change has been reverted in main already #15460, but it is not tagged yet. This leads to Chrome browser tabs crashing with the "Aw Snap!" error when running my code built with emsdk latest.
It would be nice to have a working tag soon, especially since finding the root cause for crashing browser tabs is really hard.
Thanks
The text was updated successfully, but these errors were encountered: