-
Notifications
You must be signed in to change notification settings - Fork 53
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
EXC_BAD_ACCESS when running on macOS 13 and Xcode 15b #1136
Comments
Note that I'm not getting any crashes on Xcode 14 + latest Swift 5.9 dev snapshot. |
Thanks I'll see if I can track that down - we fixed a missing lock around there, maybe I missed something |
Just FYI, checked latest Xcode 15b7 15A5229h and error is still there. |
Hm, not sure how to test it now as all of my devices been updated to macOS 14 🥲 |
Getting the same error when running from the command line but not when running from Xcode. |
After some digging I've found that it's the If you add My guess is that even though SE-0396 was implemented in Swift 5.9, the runtime on macOS 13 doesn't have it, so it leads to undefined behaviour and the program crashing. |
Description
Getting EXC_BAD_ACCESS when running on macOS 13 and Xcode 15b6 (15A5219j) specifically.
Runs perfectly on:
macOS 13 + Xcode 14
macOS 13 + Xcode 14 on Swift 5.9 DEV SNAPSHOT toolchain
macOS 14 + Xcode 15b6 (15A5219j)
Steps to reproduce
Run any simple project, e.g. https://github.com/akbashev/WorkerPoolTest
Environment
macOS 13.4.1, Xcode 15.0 Beta 6 (15A5219j)
Backtrace
The text was updated successfully, but these errors were encountered: