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
[SR-12511] Swift 5.2 / Xcode 11.4 apps crash on 32 bit devices in SingletonMetadata #54953
Comments
Comment by Alexander Serdobintsev (JIRA) We've faced the same issue on 32-bit devices (iPhone 5, iPhone 5c, iPad 4) with iOS 10. Optimization Level - Fastest, Smallest [-Os]. Our crash happens when OS switches from other thread to main: // other thread execution here (actually completionHandler called by NSURLSession)
dispatch_async(dispatch_get_main_queue(), ^{ // crash on this line!
// some code here
}); |
Comment by Uli Niggemann (JIRA) We also received thousands of crashes on iPads and iPhones with 32-Bit and iOS 9 or 10. Mainly from some google/firebase internals right on startup - recompiling with Xcode 11.3.1 seems to fix the issues. |
Comment by victor (JIRA) I figure out the real reason. |
@swift-ci create |
Thanks for reporting. We are already aware of the problem and it will be fixed in an upcoming release. |
Comment by Pedro Paulo de Amorim (JIRA) @eeckstein Hi, I might be wrong but I was able to detect the same issue on an iPhone 8 running iOS 13. https://imgur.com/a/FrQbTd7 |
Comment by Kiel (JIRA) @eeckstein Is Xcode 11.5 the upcoming release with this fix? |
kielgillard (JIRA User) yes |
Comment by Bridger Maxwell (JIRA) pp.amorim (JIRA User)I don't think that the crash you are seeing on iOS 13 is the same bug. Before we knew that this was a compiler bug with armv7 (32 bit) we thought it might be firebase/firebase-ios-sdk#4278 which was a bug caused by sqlite multithreading. Maybe that will be useful for debugging your issue. |
Comment by Pedro Paulo de Amorim (JIRA) bridger (JIRA User) That's ok. The strange part of the report is that Firebase crash log is equals to the crashes reported from arm7 devices, even the same function and line. That's why I suspect it could be a similar issue. The Issue opened at `firebase-ios-sdk` loops to this bug report. |
Environment
iPad 2 and iPad 3 on iOS 9 and 10. Xcode 11.4. Release profile.
Additional Detail from JIRA
md5: c797842ac8094b300390cbd789c763aa
Issue Description:
My app compiled with Xcode 11.4 started getting hundreds of crashes on 32 bit devices (iOS 9 and 10).
On my iPad 2 I see a crash quickly after booting the app. This is the trace:
{{ * thread #1, queue = 'com.apple.main-thread', stop reason = EXC_BAD_ACCESS (code=1, address=0x0)}}
{{ * frame #0: 0x00000000}}
{{ frame #1: 0x01394f70 libswiftCore.dylib`SingletonMetadata + 24}}
{{ frame #2: 0x013819d4 libswiftCore.dylib`__SwiftNativeNSError + 20}}
{{ frame #3: 0x013819e8 libswiftCore.dylib`_TtCs12_SwiftObject + 20}}
{{ frame #4: 0x013819d4 libswiftCore.dylib`__SwiftNativeNSError + 20}}
The crash only repros on Xcode 11.4 with the Release profile.
Most of the crashes reported by Crashlytics were unique stack traces which happened to be in third party SDKs, but I don't think the SDKs were the actual cause. I believe Crashlytics for some reason has trouble capturing the above crash trace because none of the crashes had the metadata about which thread crashed and what the crash reason was.
{{Here are a couple Github issues about this crash which were mistakenly put on the SDKs: firebase/firebase-ios-sdk#5233 (comment) https://github.com/freshdesk/freshchat-ios/issues/99 }}
The text was updated successfully, but these errors were encountered: