tomLadder / react-native-echarts-wrapper

📈Powerful React-Native ECharts Wrapper 📊
MIT License
177 stars 63 forks source link

On expo, there are multiple charts on the current page, jump to another page, the system crashes directly, I don't know what to do #68

Open Tom0115 opened 3 years ago

Tom0115 commented 3 years ago

package.json: { "main": "node_modules/expo/AppEntry.js", "scripts": { "start": "expo start", "android": "expo start --android", "ios": "expo start --ios", "web": "expo start --web", "eject": "expo eject" }, "dependencies": { "@eva-design/eva": "^2.0.0", "@highcharts/highcharts-react-native": "^3.1.2", "@react-native-community/async-storage": "^1.12.1", "@react-native-community/masked-view": "0.1.10", "@react-navigation/material-top-tabs": "^5.3.10", "@react-navigation/native": "^5.8.10", "@react-navigation/stack": "^5.12.8", "@ui-kitten/components": "^5.0.0", "@ui-kitten/eva-icons": "^5.0.0", "axios": "^0.21.0", "expo": "~39.0.2", "expo-status-bar": "~1.0.2", "react": "16.13.1", "react-dom": "16.13.1", "react-native": "https://github.com/expo/react-native/archive/sdk-39.0.4.tar.gz", "react-native-echarts-wrapper": "^2.0.0", "react-native-gesture-handler": "~1.7.0", "react-native-reanimated": "~1.13.0", "react-native-safe-area-context": "3.1.4", "react-native-screens": "~2.10.1", "react-native-svg": "9.13.6", "react-native-tab-view": "^2.15.2", "react-native-table-component": "^1.2.1", "react-native-web": "~0.13.12", "react-native-webview": "^10.10.2" }, "devDependencies": { "@babel/core": "~7.9.0" }, "private": true }

immortal-oe commented 3 years ago

In the library, the WebView component to add androidHardwareAccelerationDisabled properties, close the android hardware acceleration

kanadgodse-lh commented 2 years ago

I was having a similar issue where I was getting SIGSEGV Segmentation violation (invalid memory reference) libhwui.so I have added androidHardwareAccelerationDisabled={true} to /node_modules/react-native-echarts-wrapper/src/index.js inside <Webview and it has solved the crashing issue for me. It would be good if this library provided a way to enable or disable this prop without changing inside the library.