Increased number of libmonochrome crashes from ~1st Aug

Target Platforms Mobile
,
1

Hey!

OS: Android 13, 12, 11, 10, other
Ads Mediator: Applovin MAX

We see increased number of crashes that started around ~1st Aug (we didn’t change anything in our app). Crash is related to Android WebView (libmonochrome ). The crash is not new, some ads crash from time to time but the number increased significantly.

Maybe someone also experience increased number of similar crashes? Guys from Applovin wrote that they didn’t get any reports, maybe it is related to one of the networks OR webview

Crashed: Thread: SIGTRAP  0x0000007812dc2658
#00 pc 0x3192658 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#01 pc 0x3191d98 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#02 pc 0x6949890 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#03 pc 0x43187f0 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#04 pc 0x29f76e0 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#05 pc 0x5f423f4 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#06 pc 0x3859bb4 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#07 pc 0x3859b24 libmonochrome_64.so (BuildId: 71551fe98b8178c12bca21b0531e53b20b63408a)
#08 pc 0x18028 libutils.so (BuildId: 97f353c1a350efeb766e1e852854da85)
#09 pc 0x17b9c libutils.so (BuildId: 97f353c1a350efeb766e1e852854da85)
#10 pc 0x1689ec libandroid_runtime.so (BuildId: a34fb35e38cbccfd38d422e9a88ec8e8)
#11 pc 0x72acd1a8
#12 pc 0x72ac9578
#13 pc 0x72ac93dc
#14 pc 0x727d8ef8
#15 pc 0x458000 libart.so (BuildId: 6fc1c03912861b04885c9f2953121b6b)
#16 pc 0x48ad9c libart.so (BuildId: 6fc1c03912861b04885c9f2953121b6b)

Thread:
#00 pc 0x4fa30 libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#01 pc 0x544f8 libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#02 pc 0xba9bc libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#03 pc 0x26ca434 libil2cpp.so (__Il2CppComDelegate_Finalize_mC9F8EA94444C3AF0A43CC723A23EE4D8B7984F8C) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#04 pc 0x26c7ffc libil2cpp.so (__Il2CppComDelegate_Finalize_mC9F8EA94444C3AF0A43CC723A23EE4D8B7984F8C) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#05 pc 0x26c7ffc libil2cpp.so (__Il2CppComDelegate_Finalize_mC9F8EA94444C3AF0A43CC723A23EE4D8B7984F8C) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#06 pc 0x26c8904 libil2cpp.so (__Il2CppComDelegate_Finalize_mC9F8EA94444C3AF0A43CC723A23EE4D8B7984F8C) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#07 pc 0x26c88f4 libil2cpp.so (__Il2CppComDelegate_Finalize_mC9F8EA94444C3AF0A43CC723A23EE4D8B7984F8C) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#08 pc 0x71c640 libil2cpp.so (il2cpp::gc::FinalizerThread(void*)) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#09 pc 0x71c5d8 libil2cpp.so (il2cpp::gc::GarbageCollector::InitializeFinalizer()) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#10 pc 0x7149a0 libil2cpp.so (il2cpp::os::Thread::RunWrapper(void*)) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#11 pc 0x627ffc libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#12 pc 0x758668 libil2cpp.so (il2cpp::os::ThreadImpl::ThreadStartWrapper(void*)) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
#13 pc 0xbb6e8 libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#14 pc 0x54fdc libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#15 pc 0xbb614 libc.so (BuildId: 54071c506231d1ab2d3653b44eddcea5)
#16 pc 0x758648 libil2cpp.so (il2cpp::os::ThreadImpl::Run(void (*)(void*), void*, long)) (BuildId: bd762af0a5da4b7955ff1abdb3cfbea19932d8c0)
2

Exactly the same issue here. It suddenly started the 1st August without any changes on my side.

I’m also using AppLovin MAX.

As you may already found in your research, something similar already happened in March 2021 with a bug in the Android System Webview. Not sure it’s the same issue this time. Otherwise the only solution would be to wait until Google fix it.

Also, interesting thing, we previously had a common issue in the past : ViewTreeObserver.dispatchOnGlobalLayout crash on Android. It seems that we have a similar ad configuration. And because I didn’t found a lot of people talking about this new issue, I’m like : Is this APS SDK again ?

A little bit busy right now to deep search this issue, but I will let you know if I find something later.

3

I’m seeing a significant decrease of the crash on the 19th of August on Android Vitals (Google Play Console)

Do you see the same on your side ?

4

Hey, yes I saw that, but it increased the next day

5

@ dev-alban could we compare our ads stack? It will be easier to find the cause of crashes. I wrote to you via Conversations

6

Hello Guys, have you been able to solve this issue? We can see something simillar in our apps, big amount of crashes on various devices. I will appreciate your answear.

7

Same issue here. That crashes dropped my app ranking drastically. From #6 to #57 and reduced my audience to 20%.
If someone was able to find the solution. Please Let me know. I will appreciate it.
Using Unity 2021.3.30f1 and AppLovin Max (5.11.3) with Mintegral, FBAN and AdColony Mediation.

8

We are facing the same issue. Mostly on S22, S22 ultra, S23 and S23 ultra. Anyone found a solution?

9

Facing the same problem here using Ironsource as a mediator

10

I’m seeing a major decrease of this issue on my Android Vitals (Google Play Console) from the 13th of December.

Did you all see it too ?

11

Hey guys, any update about these issues? I’m facing the same problem here, but in my case, there is not a huge amount of crashes at least.
I’m using MAX SDK too.

12

For me, the issue is still present but only concerns 0.03% of my DAU, which is more than negligible compared to almost 4% when it was at its peak before 13th December 2023.