@lukebaker I can confirm that the crashes is related. we where seeing the Fatal signal 11 (SIGSEGV) in our production app. Our solution to fixing the problem was setting opacity: 0.99 on the actual webview and keeping overflow: hidden on the container.

@christianbach @lukebaker this crash also happens on Samsung S8 Android 8 with similar error "Fatal signal 11 (SIGSEGV) ..... (RenderThread)". when I try to navigate back from any screen included WebView, and I tried @christianbach 's fix, it is working.

Edited: the fix is working under WebView with other components. But does not fix the issue if I have the single webView for the entire screen.

@malonguwa do you really need to wrap the webview with overflow: hidden if you have a single webview covering the entire screen?

@dlindstrm cos when I navigate to my webViewScreen and then click the back button on the left top l, the app crash..... and I guess it is related to the webView component, cos this only happens when navigate back from the WebViewScreen, if no webView everything works well, but this walk around does not work in my case

Let's keep all discussion to #429! This will probably help get this solved faster 💯

@lukebaker I can confirm that the crashes is related. we where seeing the Fatal signal 11 (SIGSEGV) in our production app. Our solution to fixing the problem was setting opacity: 0.99 on the actual webview and keeping overflow: hidden on the container.

This solved the issue for me. I was getting a random crash only on android when I navigate back from a screen that was using webview in react navigation.

Only thing I was getting from error log in Android Studio was W/google-breakpad

@gamingumar Same, using opacity:0.99 on the webview somehow solves it from crashing on android

Still still persists in Hermes engine. Had to disable it also enable hardwareAcceleration on android.

Still still persists in Hermes engine. Had to disable it also enable hardwareAcceleration on android.

no, there is nothing related to Hermes engine, it is just an Chrome bug, using opacity: 0.99 can bypass this problem

`const Nav = createStackNavigator({

    IntroSlider: IntroSlider,
    Root: TabNavigator,
    LocationDetail: {screen: LocationDetail},
   .....
}, {

    mode: 'modal', //<---In my case, I added this option and it worked fine. "react-navigation-stack": "^2.0.15",
    headerMode: 'none',
},

);`

opacity: 0.99 works 👍 .
If it does not, make sure your container has at least fixed height.

This works:

<View style={{ overflow: 'hidden', width: '100%', height: 500 }}>
        <WebView style={{ opacity: 0.99 }} />
</View>

This still crashes:

<View style={{ overflow: 'hidden', flex: 1 }}>
        <WebView style={{ opacity: 0.99 }} />
</View>

If your WebView needs to be full screen just use Dimensions.get('window') instead of flex

Moved to #429.