firebase-ios-sdk
firebase-ios-sdk copied to clipboard
Crashed: com.google.firebase.crashlytics.ios.logging
Description
Crashed: com.google.firebase.crashlytics.ios.logging 0 libsystem_kernel.dylib 0x7200 __pthread_kill + 8 1 libsystem_pthread.dylib 0x71ac pthread_kill + 268 2 libsystem_c.dylib 0x20c8c abort + 180 3 libsystem_malloc.dylib 0x1df2c malloc_vreport + 908 4 libsystem_malloc.dylib 0x1e110 malloc_report + 64 5 libsystem_malloc.dylib 0x19b38 find_zone_and_free + 308 6 libsystem_blocks.dylib 0x1d6c _Block_release + 276 7 libdispatch.dylib 0x3fdc _dispatch_client_callout + 20 8 libdispatch.dylib 0xb694 _dispatch_lane_serial_drain + 672 9 libdispatch.dylib 0xc1e0 _dispatch_lane_invoke + 384 10 libdispatch.dylib 0x16e10 _dispatch_workloop_worker_thread + 652 11 libsystem_pthread.dylib 0xdf8 _pthread_wqthread + 288 12 libsystem_pthread.dylib 0xb98 start_wqthread + 8
Reproducing the issue
No response
Firebase SDK Version
10.1.0
Xcode Version
14.1
Installation Method
CocoaPods
Firebase Product(s)
Analytics, Crashlytics, Database, Firestore, Messaging, Performance
Targeted Platforms
iOS
Relevant Log Output
No response
If using Swift Package Manager, the project's Package.resolved
Expand Package.resolved
snippet
Replace this line with the contents of your Package.resolved.
If using CocoaPods, the project's Podfile.lock
Expand Podfile.lock
snippet
Replace this line with the contents of your Podfile.lock!
I couldn't figure out how to label this issue, so I've labeled it for a human to triage. Hang tight.
Hey @sspogra, this is crashing in _Block_release
, which is usually a sign of memory corruption. Can you try reproducing this crash with memory diagnostics on?
Hey @sspogra. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
@morganchen12 I am not able to reproduce it locally. Its happened only in live app.
Another same crash found
Crashed: com.google.firebase.crashlytics.ios.logging
0 libsystem_kernel.dylib 0x7200 __pthread_kill + 8
1 libsystem_pthread.dylib 0x71ac pthread_kill + 268
2 libsystem_c.dylib 0x20c8c abort + 180
3 libsystem_malloc.dylib 0x1df2c malloc_vreport + 908
4 libsystem_malloc.dylib 0x1e1d0 malloc_zone_error + 100
5 libsystem_malloc.dylib 0x186b0 nanov2_guard_corruption_detected + 44
6 libsystem_malloc.dylib 0x16acc nanov2_free_definite_size + 386
7 libsystem_blocks.dylib 0x1b08 _Block_copy + 68
8 libdispatch.dylib 0x2478 _dispatch_Block_copy + 32
9 libdispatch.dylib 0x893c dispatch_async + 56
10 libdispatch.dylib 0x893c dispatch_channel_async + 56
11 FirebaseCrashlytics 0x2a7d8 __FIRCLSUserLoggingWriteAndCheckABFiles_block_invoke + 551 (FIRCLSUserLogging.m:551)
12 libdispatch.dylib 0x3fdc _dispatch_client_callout + 20
13 libdispatch.dylib 0x139a8 _dispatch_sync_invoke_and_complete_recurse + 64
14 libdispatch.dylib 0x13428 _dispatch_sync_f_slow + 172
15 FirebaseCrashlytics 0x2a254 FIRCLSUserLoggingWriteAndCheckABFiles + 555 (FIRCLSUserLogging.m:555)
16 FirebaseCrashlytics 0x2a648 FIRCLSLogInternal + 602 (FIRCLSUserLogging.m:602)
17 FirebaseCrashlytics 0x2a52c FIRCLSLog + 418 (FIRCLSUserLogging.m:418)
18 FirebaseCrashlytics 0x2bda0 -[FIRCrashlytics log:] + 263 (FIRCrashlytics.m:263)
19 FirebaseCrashlytics 0x2be2c -[FIRCrashlytics logWithFormat:arguments:] + 273 (FIRCrashlytics.m:273)
20 AppName 0x47cdc8 specialized UserRepository.saveCrashlyticsLog(name:path:data:) + 4306849224 (
Hi @sspogra, do you have a full crash report can share with us to take a look? From the second crash, Crashlytics library is called from a closure of your app, and this seems like a memory corruption crash, can you verify do you have strong referencing cycle within your closure?
Hey @sspogra. We need more information to resolve this issue but there hasn't been an update in 5 weekdays. I'm marking the issue as stale and if there are no new updates in the next 5 days I will close it automatically.
If you have more information that will help us get to the bottom of this, just add a comment!
Since there haven't been any recent updates here, I am going to close this issue.
@sspogra if you're still experiencing this problem and want to continue the discussion just leave a comment here and we are happy to re-open this.