You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@chanphiromsok this can't be accepted as a bug report since there is no way for us to reproduce what you're describing, specifically for OOM issues, you should run an android memory profiler and understand how memory usage change / grow with time, android offers amazing tools for that, check out: https://developer.android.com/studio/profile/memory-profiler
you need to understand your app's memory footprint and what is causing the memory leak, once you identify it please submit a bug report with sample project and share your findings.
I have found an issue that my app is running foreground service for broadcast location and the process is alive every time I close and open the app the MainActivity and ScreenFragment cause memory leaks so that when the user opens the map screen it causes app crashed but unfortunately, I can not resolve it yet because I am using react-native-screens
Summary
I receive crashed report analytics from googleplay everyday cause from out of memory for mapview I use for driver app and long running
here crashed log
crashed.txt
Reproducible sample code
Steps to reproduce
long running map view keep open using internet if you stay in cold weather can not repoduce (I think)
Expected result
expect not consume hight ram for long running
Actual result
for long running map will cause the app crashed
React Native Maps Version
1.14.0
What platforms are you seeing the problem on?
Android
React Native Version
0.73.6
What version of Expo are you using?
SDK 48
Device(s)
Galaxy S10 5G,Reno10 5G,Galaxy Note10+,Galaxy A55 5G,Model:Galaxy S22 Ultra
Additional information
I use expo 50 (in selected expo version does not has 50)
The text was updated successfully, but these errors were encountered: