iOS crash due to JSC sanitizeStackForVMImpl
See original GitHub issue🐛 Bug Report
This seems to only occur on iOS 11 as we’ve only seen crash reports for 11.* versions.
Thread 2
#0 (null) in sanitizeStackForVMImpl ()
#1 (null) in JSC::Heap::finishChangingPhase(JSC::GCConductor) ()
#2 (null) in JSC::Heap::runCurrentPhase(JSC::GCConductor, JSC::CurrentThreadState*) ()
#3 (null) in JSC::Heap::collectInMutatorThread() ()
#4 (null) in JSC::Heap::stopIfNecessarySlow() ()
#5 (null) in JSC::Heap::acquireAccessSlow() ()
#6 (null) in JSC::JSLock::didAcquireLock() ()
#7 (null) in JSC::JSLockHolder::JSLockHolder(JSC::ExecState*) ()
#8 (null) in JSObjectMakeArray ()
#9 (null) in facebook::jsc::JSCRuntime::createArray(unsigned long) ()
#10 (null) in facebook::jsi::valueFromDynamic(facebook::jsi::Runtime&, folly::dynamic const&) ()
#11 (null) in std::__1::__function::__func<facebook::react::JSIExecutor::callFunction(std::__1::basic_string<ch... ()
#12 (null) in void std::__1::__invoke_void_return_wrapper<void>::__call<void (*&)(std::__1::function<void ()> c... ()
#13 (null) in facebook::react::JSIExecutor::callFunction(std::__1::basic_string<char, std::__1::char_traits<cha... ()
#14 (null) in std::__1::function<void (YGNode*)>::operator()(YGNode*) const ()
#15 (null) in facebook::react::tryAndReturnError(std::__1::function<void ()> const&) ()
#16 (null) in facebook::react::RCTMessageThread::tryFunc(std::__1::function<void ()> const&) ()
#17 (null) in __CFRUNLOOP_IS_CALLING_OUT_TO_A_BLOCK__ ()
#18 (null) in __CFRunLoopDoBlocks ()
#19 (null) in __CFRunLoopRun ()
#20 (null) in CFRunLoopRunSpecific ()
#21 (null) in +[RCTCxxBridge runRunLoop] ()
#22 (null) in __NSThread__start__ ()
#23 (null) in _pthread_body ()
#24 (null) in _pthread_start ()
#25 (null) in thread_start ()
To Reproduce
Expected Behavior
Code Example
Environment
React Native Environment Info:
System:
OS: macOS High Sierra 10.13.6
CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz
Memory: 290.95 MB / 16.00 GB
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 11.8.0 - /usr/local/bin/node
Yarn: 1.13.0 - /usr/local/bin/yarn
npm: 6.5.0 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 12.1, macOS 10.14, tvOS 12.1, watchOS 5.1
Android SDK:
API Levels: 24, 25, 26, 27, 28
Build Tools: 23.0.3, 25.0.3, 26.0.1, 26.0.3, 27.0.3, 28.0.1, 28.0.2, 28.0.3
System Images: android-23 | Google APIs Intel x86 Atom, android-26 | Google Play Intel x86 Atom, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
IDEs:
Android Studio: 3.3 AI-182.5107.16.33.5264788
Xcode: 10.1/10B61 - /usr/bin/xcodebuild
npmPackages:
react: 16.8.2 => 16.8.2
react-native: 0.58.5 => 0.58.5
npmGlobalPackages:
react-native-cli: 2.0.1
Issue Analytics
- State:
- Created 4 years ago
- Reactions:9
- Comments:5 (1 by maintainers)
Top Results From Across the Web
Crash on iOS 15 devices happens mostly in background
Hi,. Our application is currently crashing in production, only for users with iPhone and iPad running iOS and iPadOS 15 through all releases....
Read more >186827 – Crash in sanitizeStackForVMImpl sometimes when ...
Summary: Crash in sanitizeStackForVMImpl sometimes when switching threads with ... JavaScriptCore 0x0000000117548794 JSC::Heap::stopIfNecessarySlow() + 68 3 ...
Read more >iOS Production build (EAS, Expo) crashes directly after ...
I have a problem with the IOS part of my ReactNative App. The Android ... it doesn't lead to a build failure and...
Read more >Timeline – WebKit - WebKit Trac
simulated crash, explaining that it is invalid for any scene-based app to call -statusBarOrientation. To fix this, we adjust the deviceOrientation helper in ......
Read more >Debug IOS Crashes Efficiently With Datadog RUM
Unsurprisingly, application crashes due to fatal errors can be a major pain point for iOS users. Recent research shows that roughly 20 ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’m using the latest release 0.59.8 and it’s still happening.
I am closing this issue because it does not appear to have been verified on the latest release, and there has been no followup in a while.
If you found this thread after encountering the same issue in the latest release, please feel free to create a new issue with up-to-date information by clicking here.