Closed kumaresan closed 4 years ago
google-oss-bot
commented
4 years ago I found a few problems with this issue:
morganchen12
commented
4 years ago From what I understand com.google.firebase.crashlytics.ios.exception is the mach exception handler thread and a crash in that thread is not indicative of Crashlytics causing the crash but rather intercepting it after some other thread has crashed.
@samedson can definitely explain in more detail than I can, but this crash looks like a normal OOM crash. If that's the case, Firebase won't be able to fix the crash in your app--you'll have to look at your app's allocations and find a way to avoid allocating unnecessary memory.
samedson
commented
4 years ago Yeah what Morgan said is correct - sometimes our own crash capturing is collected in the report. I would recommend you look at the second stacktrace to identify the root cause, and look into your memory allocations.
kumaresan
commented
4 years ago Since the issue could not be replicated, it's not possible to a debugging on the crash. One more Crash reported. Stack trace below. We have upgraded the FirebaseCrashlytics version to 4.0.0 (Stable version).
Fatal Exception: std::bad_alloc
std::bad_allocCrashed: com.google.firebase.crashlytics.ios.exception
SIGABRT ABORT 0x0000000199ea2d88
std::__terminate(void (*)())Crashed: com.google.firebase.crashlytics.ios.exception
0 My Application 0x105488c64 FIRCLSProcessRecordAllThreads + 392 (FIRCLSProcess.c:392)
1 My Application 0x105489048 FIRCLSProcessRecordAllThreads + 423 (FIRCLSProcess.c:423)
2 My Application 0x10547f8ac FIRCLSHandler + 34 (FIRCLSHandler.m:34)
3 My Application 0x10547aef4 __FIRCLSExceptionRecord_block_invoke + 218 (FIRCLSException.mm:218)
4 libdispatch.dylib 0x199d73524 _dispatch_client_callout + 16
5 libdispatch.dylib 0x199d571fc _dispatch_lane_barrier_sync_invoke_and_complete + 56
6 My Application 0x10547a68c FIRCLSExceptionRecord + 225 (FIRCLSException.mm:225)
7 My Application 0x10547a32c FIRCLSTerminateHandler() + 285 (FIRCLSException.mm:285)
8 libc++abi.dylib 0x199e7614c std::__terminate(void (*)()) + 16
9 libc++abi.dylib 0x199e78e58 __cxa_rethrow + 144
10 libobjc.A.dylib 0x199dcfd80 objc_exception_rethrow + 40
11 CoreFoundation 0x19a025ca0 CFRunLoopRunSpecific + 532
12 GraphicsServices 0x1a416f38c GSEventRunModal + 160
13 UIKitCore 0x19e15822c UIApplicationMain + 1932
14 My Application 0x104ce4604 main + 4311467524 (<compiler-generated>:4311467524)
15 libdyld.dylib 0x199ead800 start + 4@kumaresan can you post the other threads in the stacktrace?
google-oss-bot
commented
4 years ago Hey @kumaresan. 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!
kumaresan
commented
4 years ago The issue did not occur again, after moving to the stable version of Firebase/Crashlytics. Thanks for your assistance.
[REQUIRED] Step 1: Describe your environment
[REQUIRED] Step 2: Describe the problem
Firebase Crashlytics crashing our Application Crashed: com.google.firebase.crashlytics.ios.exception
Steps to reproduce:
The iOS application was shared with a closed user group (customers) via Testflight and hence we could not replicate the issue. But the information that we received was there were two crashes noticed by the user. But we got only one crash logged n our Crashlytics console. Looking deeper, the stack trace looks like it came from Firebase Crashlytics SDK itself while trying to submit the crash. We have upgraded the SDK to a 4.0.0 stable version now. Since, We have planned to go live after this CUG testing we wanted to report this issue.
Exception
Stack Trace:
Exception
Stacktrace