EXC_CORPSE_NOTIFY iOS crash when using native modules #19107
Comments
|
I was just able to reproduce what I think is the same issue in the simulator by pressing ⌘R a few times:
Interestingly, the stack trace is identical, but this says I tried to inspect some of the variables in lldb, but then Xcode crashed 🙄 |
|
Hey there, it looks like there has been no activity on this issue recently. Has the issue been fixed, or does it still require the community's attention? This issue may be closed if no further activity occurs. You may also label this issue as "For Discussion" or "Good first issue" and I will leave it open. Thank you for your contributions. |
stale
bot
added
the
Stale
|
Issue still persists in 0.56 |
stale
bot
removed
the
Stale
|
seems like we are seeing this: |
|
Good Work
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Jim Bartek <notifications@github.com>
Sent: Friday, September 21, 2018 4:38:24 PM
To: facebook/react-native
Cc: Subscribed
Subject: Re: [facebook/react-native] EXC_CORPSE_NOTIFY iOS crash when using native modules (#19107)
seems like we are seeing this:
OS Version: iPhone OS 11.2 (15C114)
Baseband Version: 6.30.04
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 21
Application Specific Information:
abort() called
Filtered syslog:
None found
Thread 21 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue
Thread 21 Crashed:
0 libsystem_kernel.dylib 0x00000001824282e8 __pthread_kill + 8
1 libsystem_pthread.dylib 0x000000018253d2f8 pthread_kill$VARIANT$mp + 396
2 libsystem_c.dylib 0x0000000182396fbc abort + 140
3 libc++abi.dylib 0x0000000181b33068 __cxa_bad_cast + 0
4 libc++abi.dylib 0x0000000181b33210 default_unexpected_handler+ 8720 () + 0
5 libobjc.A.dylib 0x0000000181b5c810 _objc_terminate+ 34832 () + 124
6 TechApp Beta 0x000000010124e6ec 0x1011f0000 + 386796
7 libc++abi.dylib 0x0000000181b4b54c std::__terminate(void (*)+ 107852 ()) + 16
8 libc++abi.dylib 0x0000000181b4aea8 __cxxabiv1::exception_cleanup_func+ 106152 (_Unwind_Reason_Code, _Unwind_Exception*) + 0
9 libobjc.A.dylib 0x0000000181b5c65c _objc_exception_destructor+ 34396 (void*) + 0
10 TechApp Beta 0x00000001012d9560 0x1011f0000 + 955744
11 TechApp Beta 0x00000001012d90a8 0x1011f0000 + 954536
12 libdispatch.dylib 0x0000000182292a54 _dispatch_call_block_and_release + 24
13 libdispatch.dylib 0x0000000182292a14 _dispatch_client_callout + 16
14 libdispatch.dylib 0x000000018229c96c _dispatch_queue_serial_drain$VARIANT$mp + 528
15 libdispatch.dylib 0x000000018229d2fc _dispatch_queue_invoke$VARIANT$mp + 340
16 libdispatch.dylib 0x000000018229dd20 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 404
17 libdispatch.dylib 0x00000001822a603c _dispatch_workloop_worker_thread$VARIANT$mp + 644
18 libsystem_pthread.dylib 0x000000018253af1c _pthread_wqthread + 932
19 libsystem_pthread.dylib 0x000000018253ab6c start_wqthread + 4
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#19107 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADe8y0qY1BVl5pObSlXQQvDlxLdp-RtBks5udVxQgaJpZM4TwA4P>.
|
|
Good work good work good work good work good work good work
Get Outlook for Android<https://aka.ms/ghei36>
…________________________________
From: Jim Bartek <notifications@github.com>
Sent: Friday, September 21, 2018 4:38:24 PM
To: facebook/react-native
Cc: Subscribed
Subject: Re: [facebook/react-native] EXC_CORPSE_NOTIFY iOS crash when using native modules (#19107)
seems like we are seeing this:
OS Version: iPhone OS 11.2 (15C114)
Baseband Version: 6.30.04
Report Version: 104
Exception Type: EXC_CRASH (SIGABRT)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFY
Triggered by Thread: 21
Application Specific Information:
abort() called
Filtered syslog:
None found
Thread 21 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue
Thread 21 Crashed:
0 libsystem_kernel.dylib 0x00000001824282e8 __pthread_kill + 8
1 libsystem_pthread.dylib 0x000000018253d2f8 pthread_kill$VARIANT$mp + 396
2 libsystem_c.dylib 0x0000000182396fbc abort + 140
3 libc++abi.dylib 0x0000000181b33068 __cxa_bad_cast + 0
4 libc++abi.dylib 0x0000000181b33210 default_unexpected_handler+ 8720 () + 0
5 libobjc.A.dylib 0x0000000181b5c810 _objc_terminate+ 34832 () + 124
6 TechApp Beta 0x000000010124e6ec 0x1011f0000 + 386796
7 libc++abi.dylib 0x0000000181b4b54c std::__terminate(void (*)+ 107852 ()) + 16
8 libc++abi.dylib 0x0000000181b4aea8 __cxxabiv1::exception_cleanup_func+ 106152 (_Unwind_Reason_Code, _Unwind_Exception*) + 0
9 libobjc.A.dylib 0x0000000181b5c65c _objc_exception_destructor+ 34396 (void*) + 0
10 TechApp Beta 0x00000001012d9560 0x1011f0000 + 955744
11 TechApp Beta 0x00000001012d90a8 0x1011f0000 + 954536
12 libdispatch.dylib 0x0000000182292a54 _dispatch_call_block_and_release + 24
13 libdispatch.dylib 0x0000000182292a14 _dispatch_client_callout + 16
14 libdispatch.dylib 0x000000018229c96c _dispatch_queue_serial_drain$VARIANT$mp + 528
15 libdispatch.dylib 0x000000018229d2fc _dispatch_queue_invoke$VARIANT$mp + 340
16 libdispatch.dylib 0x000000018229dd20 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 404
17 libdispatch.dylib 0x00000001822a603c _dispatch_workloop_worker_thread$VARIANT$mp + 644
18 libsystem_pthread.dylib 0x000000018253af1c _pthread_wqthread + 932
19 libsystem_pthread.dylib 0x000000018253ab6c start_wqthread + 4
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#19107 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADe8y0qY1BVl5pObSlXQQvDlxLdp-RtBks5udVxQgaJpZM4TwA4P>.
|
|
GovLoop
Get Outlook for Android<https://aka.ms/ghei36>
From: Jim Bartek
Sent: Friday, September 21, 4:38 PM
Subject: Re: [facebook/react-native] EXC_CORPSE_NOTIFY iOS crash when using native modules (#19107)
To: facebook/react-native
Cc: Subscribed
seems like we are seeing this:
OS Version: iPhone OS 11.2 (15C114) Baseband Version: 6.30.04 Report Version: 104 Exception Type: EXC_CRASH (SIGABRT) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Triggered by Thread: 21 Application Specific Information: abort() called Filtered syslog: None found Thread 21 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Thread 21 Crashed: 0 libsystem_kernel.dylib 0x00000001824282e8 __pthread_kill + 8 1 libsystem_pthread.dylib 0x000000018253d2f8 pthread_kill$VARIANT$mp + 396 2 libsystem_c.dylib 0x0000000182396fbc abort + 140 3 libc++abi.dylib 0x0000000181b33068 __cxa_bad_cast + 0 4 libc++abi.dylib 0x0000000181b33210 default_unexpected_handler+ 8720 () + 0 5 libobjc.A.dylib 0x0000000181b5c810 _objc_terminate+ 34832 () + 124 6 TechApp Beta 0x000000010124e6ec 0x1011f0000 + 386796 7 libc++abi.dylib 0x0000000181b4b54c std::__terminate(void (*)+ 107852 ()) + 16 8 libc++abi.dylib 0x0000000181b4aea8 __cxxabiv1::exception_cleanup_func+ 106152 (_Unwind_Reason_Code, _Unwind_Exception*) + 0 9 libobjc.A.dylib 0x0000000181b5c65c _objc_exception_destructor+ 34396 (void*) + 0 10 TechApp Beta 0x00000001012d9560 0x1011f0000 + 955744 11 TechApp Beta 0x00000001012d90a8 0x1011f0000 + 954536 12 libdispatch.dylib 0x0000000182292a54 _dispatch_call_block_and_release + 24 13 libdispatch.dylib 0x0000000182292a14 _dispatch_client_callout + 16 14 libdispatch.dylib 0x000000018229c96c _dispatch_queue_serial_drain$VARIANT$mp + 528 15 libdispatch.dylib 0x000000018229d2fc _dispatch_queue_invoke$VARIANT$mp + 340 16 libdispatch.dylib 0x000000018229dd20 _dispatch_root_queue_drain_deferred_wlh$VARIANT$mp + 404 17 libdispatch.dylib 0x00000001822a603c _dispatch_workloop_worker_thread$VARIANT$mp + 644 18 libsystem_pthread.dylib 0x000000018253af1c _pthread_wqthread + 932 19 libsystem_pthread.dylib 0x000000018253ab6c start_wqthread + 4
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub<#19107 (comment)>, or mute the thread<https://github.com/notifications/unsubscribe-auth/ADe8y0qY1BVl5pObSlXQQvDlxLdp-RtBks5udVxQgaJpZM4TwA4P>.
|
|
+1 |
|
has some one fixed this issue ?????? |
|
In my case, when Release I got a message like: |
|
I'm still hitting this issue in 0.58.4, crashing in release mode but working fine in debug mode |
|
Hello there 👋 this issue doesn't have a repro (which means, a react-native init-ed project with the minimal changes that leads to creating the same issue you are reporting). Unfortunately, I have no way of helping you in a meaningful way – there is no easy way for me to recreate the situation and check that the issue reported is still there when changing the code. We need a exact code of a native module and the payload that is causing issue, otherwise it's hard. Because of this, we are going to close this issue - but if a repro is shared, we are happy to reopen it 🤗 |
|
My original report filed almost a year ago included steps to reproduce. Lots of people have commented that they reproduced it. Did you try it? |
|
Same here |
|
@getaaron we noticed crashes when we were heavily downloading data across multiple threads and eating up both cpu and storage I/O and iOS kills the app. The only way to find that the device was killing the app (vs. the app crashing) was to plug in the iPad and pull logs from the device directly vs. with xCode. We sorted this out when no crash reports were showing up in App Center, because the app was getting force quit, not crashing. We had to better handle our data downloads and sequence them, downloading ~200 MB of data on first login (offline first corporate app). I'm kind of noob though and we have had a variety of problems so YMMV. |
|
@getaaron Did you ever find a solution? My crash report looks similar to yours. App worked fine in build mode and in 3 different devices but crashed on appstore review. |
|
@solixmedia We rewrote the app in Swift and got rid of React Native. |
|
@getaaron Thanks for replying. Kind of discouraging to hear. |
1 similar comment
|
@getaaron Thanks for replying. Kind of discouraging to hear. |
|
We're having the same issue in React Native 59.9 We do connect to quite a few native-modules:
From third party:
Edit:
Never ever have I experienced something like this, nor do I have any clue what could be the cause. |
|
Same situation here. I was doing well programming in react native, but with this I dont know what to do. Hope any help guys. Incident Identifier: 92794F51-C4E1-437D-9287-1D4871DEC991 Date/Time: 2019-09-23 18:57:42.1148 -0500 Exception Type: EXC_CRASH (SIGABRT) Application Specific Information: Last Exception Backtrace: Thread 0 name: Dispatch queue: com.apple.main-thread Thread 1 name: Dispatch queue: com.facebook.react.ExceptionsManagerQueue Thread 2 name: com.apple.uikit.eventfetch-thread Thread 3: Thread 4 name: com.facebook.react.JavaScript Thread 5 name: JavaScriptCore bmalloc scavenger Thread 6 name: com.apple.CoreMotion.MotionThread Thread 7: Thread 8 name: Heap Helper Thread Thread 9: Thread 10 name: com.apple.NSURLConnectionLoader Thread 11 name: JSC Heap Collector Thread Thread 1 crashed with ARM Thread State (64-bit): Binary Images: EOF |
|
is there any solution for this issue? facing same issue in review process in appstore. with real devices and emulators everything working perfectly. but when it put as new production release they are rejecting build and crash reports same as this report. |
|
Think this issue should be re-opened as there seems to be more people getting this issue, including myself? |
|
I have the same issue when navigating a different scene in my app but I don't know what causes the problem. Actually there is no problem when testing on simulator or getting build to my phone from Xcode. However when I get ipa file and upload to Diawi or publishing via TestFlight there is this problem. I changed codes but I couldn't solve the problem yet. Is there any solution? |
|
@keremaydin52 this solution worked for me |
|
@MrKriegler Thanks mate. I have added Firebase Crashlytics today and found that the problem is due to react-native-gesture-handler. I was just looking for the solution and saw your comment. |
The app intermittently crashes when resolving or rejecting a promise in a native module. Possibly related to #5011.
This reproduces with several native modules so I don't think it's related to a specific module.
Environment
Steps to Reproduce
Expected Behavior
I expect the data to flow back and forth as documented.
Actual Behavior
The app intermittently crashes with what looks like a memory issue.
From my observation I think it happens when resolving or rejecting a promise from Objective-C.
Here's a screenshot from the crash organizer. Note that the crash occurred on thread 10, not the main thread:
So it looks like it's somewhere in this code:
react-native/React/CxxModule/RCTNativeModule.mm
Lines 86 to 115 in 26684cf
I see that code can throw this exception:
But I don't see that error anywhere in the crash log so I'm not sure where to find it. I'm not sure if this was the actual exception, since the crash report says
EXC_CORPSE_NOTIFYso it may be a red herringThe text was updated successfully, but these errors were encountered: