SIGSEGVMainActivity Segmentation violation (invalid memory reference)

[efstathiosntonas]

Getting this on Google Pixel 5 Android 12 during app startup. It crashed 3 times in a row and the 4th time the app opened fine.

module version: 0.1.5

SIGSEGVMainActivity
Segmentation violation (invalid memory reference)

/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:303568 0x6dd3ab61d0	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:411376 0x6dd3ad06f0	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:214448 0x6dd3aa05b0	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:484684 0x6dd3ae254c	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:195512 0x6dd3a9bbb8	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes.so:157616 0x6dd3a927b0	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!libhermes-executor-common-release.so:103304 facebook::jsi::RuntimeDecorator<facebook::jsi::Runtime, facebook::jsi::Runtime>::createFunctionFromHostFunction(facebook::jsi::PropNameID const&, unsigned int, std::__ndk1::function<facebook::jsi::Value (facebook::jsi::Runtime&, facebook::jsi::Value const&, facebook::jsi::Value const*, unsigned long)>)	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhermes-executor-common-release.so:100336 0x6dcb6187f0	
/data/app/~~hhSLSPhVIdBgg4tixMbrsw==/com.XXXXXXX-rW9c2P1xwsE3xsO-_5SMjA==/base.apk!/lib/arm64-v8a/libhashing.so:471245897292 RNHashing::installHashing(facebook::jsi::Runtime&)	

[TheRogue76]

Hey @efstathiosntonas. Can you send the version of React Native that you are using with this? and the full adb and metro log? I'm in a bit of a mess right now, but I'm going to try to find some time to test it out. Is this in dev or in release mode?

[TheRogue76]

Also can you send the code segment that causes this issue? which method is being called?

[efstathiosntonas]

Hey @TheRogue76, sorry for not providing more info. My bad.

I'm using react-native 0.67.4, the bug showed up in release mode and it came through bugsnag so I don't have any logcat. The method being called is sha1 but the crash happened during app launch, not while calling this method so I don't think we should blame the method. I cannot replicate it my self since I don't have access to a Pixel 5, on emulator on dev mode works fine.

This is the breadcrumb:

[efstathiosntonas]

@TheRogue76 I'll ask for logcats from our QA company, hopefully they have them.