Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OOM gms policy maps core dynamite #5062

Closed
chanphiromsok opened this issue May 22, 2024 · 3 comments
Closed

OOM gms policy maps core dynamite #5062

chanphiromsok opened this issue May 22, 2024 · 3 comments
Labels
bug Something isn't working cannot reproduce Issue is not reproducible

Comments

@chanphiromsok
Copy link

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

<MapView
          initialCamera={initialCamera}
          ref={mapRef}
          showsCompass={false}
          onPanDrag={() => {
            cancelAnimationFrame(animationIdRef.current);
          }}
          paddingAdjustmentBehavior="never"
          style={mapStyle}
          provider={PROVIDER_GOOGLE}
          scrollDuringRotateOrZoomEnabled={false}
          onTouchEnd={() => {
            delayFollowUserLocationUntil.current = Date.now() + 5000;
          }}
          customMapStyle={customMap}>
          <ArrowMarker onLocationChange={onLocationChange} />
        </MapView>
      </Center>

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)

@chanphiromsok chanphiromsok added the bug Something isn't working label May 22, 2024
@salah-ghanim
Copy link
Collaborator

@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.

@salah-ghanim salah-ghanim added the cannot reproduce Issue is not reproducible label May 24, 2024
@joseestrella89
Copy link

joseestrella89 commented Jun 13, 2024

I am having the same issue. Currently I am running my app in an android emulator.

"react-native": "0.73.1",
"react-native-maps": "1.9.1",

Captura de pantalla 2024-06-13 a la(s) 4 27 30 p m

@chanphiromsok
Copy link
Author

chanphiromsok commented Jun 14, 2024

I am having the same issue. Currently I am running my app in an android emulator.

"react-native": "0.73.1", "react-native-maps": "1.9.1",

Captura de pantalla 2024-06-13 a la(s) 4 27 30 p m

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

you can check it here I just open issue in react-native-screen software-mansion/react-native-screens#2179

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working cannot reproduce Issue is not reproducible
Projects
None yet
Development

No branches or pull requests

3 participants