So many OutOfMemoryError on Android 10

[0xera]

• Android Studio version: No matter
• Firebase Component: Config, Analytics, Crashlytics, Performance
• Component version: 29.3.0, 30.4.1

I have a lot of OOM after updating the SDK from version 29.3.0 to 30.4.1. The number of OOM increased 5 times on devices running Android 10, and decreased on Android 12 and 11. After downgrading the version, I observe that OOM decreases on Android 10, and Android 11, 12 began to grow again. I'm afraid to upgrade to the new version. Crashes are recorded in AppGallery:

java.lang.OutOfMemoryError error: pthread_create error (1040 KB stack): Try again
in java.lang.Thread.nativeCreate(native method)

The error occurs in Firebase Analytics, Performance and Config

[argzdev]

HI @0xera, thanks for reporting. It might be difficult to pin point which Firebase product is causing the OOM. In your case, I recommend using the underlying version of each Firebase product you're using within BoM for now instead of using com.google.firebase:firebase-bom as a whole. You may see the specified version of each product in our release notes according to BoM version. Then update your versions individually, and see which product at which version is causing the OOM. I know this is a lot of work on your side, but I think this is the only way to pin point which product at which version is causing the issue.

I'll mark this as needs-info for now. Don't worry if the issue closes due to stale, we can always reopen this once we have new information. Thanks!

[0xera]

HI. @argzdev, do you have some OOM trackers in your libraries? I see a lot of issues about it

[argzdev]

There were OOM issues in the past, but those are from Firebase Auth, and Firebase Messaging. However, you're not using those libraries so I don't think that's causing you issues.

You could try using the memory-profiler tool of Android Studio. It might give you a hint what's consuming a lot of memory.

Also do you have any code snippet related to Analytics, Performance, Crashlytics, or Remote Config? Any chance you could share them with us? Or if you could provide a minimal repro of the issue, then that'll help us a lot investigating this. Thanks!

[0xera]

I can't reproduce. Only metrics and obfuscated stack traces in AppGallery like:

at java.lang.Thread.nativeCreate(Native Method)
	at java.lang.Thread.start(Thread.java:893)
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:975)
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1391)
	at xsna.ogy.C(Unknown Source:7)
	at com.google.firebase.perf.metrics.Trace.stop(SourceFile:93)
	at xsna.u1d.onFragmentPaused(SourceFile:103)
	at androidx.fragment.app.g.f(SourceFile:49)
	at androidx.fragment.app.g.f(SourceFile:18)
	at androidx.fragment.app.h.n(SourceFile:33)
	at androidx.fragment.app.h.m(SourceFile:126)
	at androidx.fragment.app.j.r(SourceFile:31)
	at androidx.fragment.app.FragmentManager.U0(SourceFile:33)
	at androidx.fragment.app.FragmentManager.U(SourceFile:10)
	at androidx.fragment.app.FragmentManager.O(Unknown Source:1)


at java.lang.Thread.nativeCreate(Native Method)
	at java.lang.Thread.start(Thread.java:893)
	at java.util.concurrent.ThreadPoolExecutor.addWorker(ThreadPoolExecutor.java:975)
	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1382)
	at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:118)
	at java.util.concurrent.Executors$DelegatedExecutorService.submit(Executors.java:640)
	at xsna.hs2$a.b(SourceFile:84)
	at xsna.hs2$a.apply(Unknown Source:0)
	at xsna.tu9.l(SourceFile:55)
	at xsna.c08.k(SourceFile:27)
	at xsna.c08.l(Unknown Source:6)
	at xsna.c08.J(SourceFile:14)
	at com.google.firebase.perf.metrics.Trace.start(SourceFile:5)
	at xsna.u1d.onFragmentResumed(SourceFile:40)
	at androidx.fragment.app.g.i(SourceFile:49)

AppGallery's report says that phones have enough memory and thread count not big (compared with our metrics).
I noticed that error happens when phone go to foreground or background and thread creates in lifecycle callbacks

[argzdev]

Looking at your stacktrace, it shows that the issue might be due to com.google.firebase.perf.metrics.Trace.stop. I see an issue that might be similar to your case #4146. Could you try using the latest version 20.3.0 for Firebase Performance and see if that helps with your issue? Thanks