EXC_BAD_ACCESS Attempted to dereference garbage pointer RN 0.61.5
See original GitHub issueEXC_BAD_ACCESS Attempted to dereference garbage pointer 0xa2557b1a9d60.
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:61:14 loadApplication
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/ReactCommon/cxxreact/Instance.cpp:95:5 loadScriptFromString
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1336:29 __51-[RCTCxxBridge executeApplicationScript:url:async:]_block_invoke
/Applications/Xcode_11.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/../include/c++/v1/functional:1799:16 facebook::react::tryAndReturnError(std::__1::function<void ()> const&)
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:276:20 -[RCTCxxBridge _tryAndHandleError:]
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1319:3 -[RCTCxxBridge executeApplicationScript:url:async:]
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:1299:3 -[RCTCxxBridge enqueueApplicationScript:url:onComplete:]
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:915:5 -[RCTCxxBridge executeSourceCode:sync:]
/Users/runner/runners/2.160.1/work/1/s/node_modules/react-native/React/CxxBridge/RCTCxxBridge.mm:390:7 __21-[RCTCxxBridge start]_block_invoke_2
/usr/lib/system/libdispatch.dylib __dispatch_call_block_and_release
/usr/lib/system/libdispatch.dylib __dispatch_client_callout
/usr/lib/system/libdispatch.dylib __dispatch_root_queue_drain
/usr/lib/system/libdispatch.dylib __dispatch_worker_thread2
/usr/lib/system/libsystem_pthread.dylib __pthread_wqthread
React Native version: react-native: 0.61.5 => 0.61.5
Steps To Reproduce
- Submit to app store in release mode
- Happens intermittently in approximately 1/20 boots
It’s hard to determine a reliable way to reproduce, but we receive crash reports about this issue.
Issue Analytics
- State:
- Created 4 years ago
- Reactions:20
- Comments:5
Top Results From Across the Web
iOS EXC_BAD_ACCESS Attempted to dereference garbage ...
My first attempt at answer wasn't nearly detailed enough to be helpful - my apologies. Let's try again. Based on the App Specific...
Read more >Crash after block release, but thr… | Apple Developer Forums
Code Block. EXC_BAD_ACCESS · Attempted to dereference garbage pointer 0x20. 0libobjc.A.dylib_objc_release. 1libsystem_blocks.dylibBlock_release.
Read more >Fixing an Unfixable Bug | Develop with Dillon
The error message was EXC_BAD_ACCESS , with this detail: Attempted to dereference garbage pointer 0x10. The address of the garbage pointer ...
Read more >EXC_BAD_ACCESS error in 1.3.3 - Zoom Developer Forum
When I'm trying to get one of Zoom's callbacks I tend to get an error instead: ... Attempted to dereference garbage pointer 0x165e15957400....
Read more >RepairShopr - Bountysource
Problem comes when I try to overwrite the current signature with a new one. ... EXC_BAD_ACCESS Attempted to dereference garbage pointer 0x1cc.
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 FreeTop 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
Top GitHub Comments
We are still experiencing this crash on a regular basis.
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please feel free to create a new issue with up-to-date information.