App Crashing with AdMob on Android 15 (16KB Page Size Emulator) - Seeking Help!

[Bilan]

Hello !

I'm facing a strange and persistent issue while developing my app using Java, and I'm hoping to get some insights or guidance from you all. My app is very simple, currently containing only an AdMob banner ad for testing purposes.

Problem Confirmation (Root Cause Isolation):
I've performed extensive testing to pinpoint the source of the problem:

My app's core code works perfectly fine and does not crash when run by itself without AdMob ads.

The crash only occurs when AdMob ads are added to the app.

To confirm this, I created a new, minimalistic test app containing only AdMob ads (just a banner), and this test app crashed in the exact same manner. This conclusively confirms that AdMob ads are the direct cause of the crash.

The Issue:
The application experiences a full Native Crash when attempting to display an AdMob banner ad. The crash does not happen immediately, but occurs after a variable period ranging from approximately 30 seconds to 12 minutes after the app starts and the ad appears, leading to the app closing unexpectedly. This crash specifically happens on an Android 15 (API level 35) emulator that uses a 16KB Page Size image, which is a specific configuration for some system images.

Crash Details (from Tombstone file):
The crash stack trace indicates a Fatal signal 5 (SIGTRAP) with fault addr 0x0 in the MemoryInfra thread, within the com.google.android.gms process (Google Play Services process). Most frames in the backtrace point to the library /data/app/.../TrichromeLibrary.apk!libmonochrome_64.so, strongly suggesting the issue lies within the WebView component or Google Play Services used by ads to render content.

The Puzzling Observation (What we've discovered):
After extensive testing, I've made a crucial discovery:

The issue occurs: on an Android 15 emulator (with 16KB Page Size settings).

The issue DOES NOT occur at all: on an Android 16 emulator (with the exact same 16KB Page Size settings)!



What I've tried so far:

I am using the latest stable version of the Google Mobile Ads SDK.

I've correctly initialized the AdMob SDK once at app startup.

I'm using a test Ad Unit ID for the banner.



Testing Environment Details:

Affected Device: Pixel 9 Pro emulator (AVD: Pixel_9_Pro)

Android Version: Android 15 (API level 35) - 16KB Page Size (emu64xa16k:15)

Emulator Version: 35.6.11-13610412

Host Operating System: Windows 10 Pro

GPU: NVIDIA GeForce GTX 960

Has anyone else encountered a similar issue on Android 15? Do you have any additional suggestions to resolve this problem, or is this a known bug in this specific Android/WebView version? Any help or guidance would be greatly appreciated!

I will attach a video demonstrating the crash and the full tombstone file for more details.

Thank you very much in advance!

[Mobile Ads SDK Forum Advisor]

Hi Bilan,

Thank you for contacting the Mobile Ads SDK Support team.

Thanks for the thorough explanation.Unfortunately we are unable to replicate the crash and Could you please confirm if you've been able to reproduce this behavior within our BannerExample after adding the relevant code? If so, please share the following details to help us investigate further and provide a solution:

• app ID and ad unit ID
• Please share your sample project where the issue is reproducible

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files with me by performing the following steps:

1. Navigate to
https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001rh7PAIAY&entry.80707362=00316952

2. Fill out all fields, and attach your file(s).

3. Please reply back on this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               
[2025-07-03 15:20:36Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rh7PA:ref" (ADR-00316952)

[Bilan]

Dear Mobile Ads SDK Support Team,

Thank you for your response.

I have followed your instructions and uploaded the sample project that reproduces the issue via the Google Form link you provided.

As requested, here are the details:

App ID: ca-app-pub-3940256099942544~3419835254 (Default test ID)

Ad Unit ID: ca-app-pub-3940256099942544/6300978111 (Default Banner test ID)

Regarding the application's behavior:

The application runs stably on standard Android 15 (4KB page size) devices/emulators.

The application runs stably on standard Android 16 (4KB page size) devices/emulators.

The application also runs stably on Android 16 with a 16KB page size system image.

However, on the Android 15 (API 35) system image with a 16KB page size, the application closes unexpectedly by itself. This can happen immediately after launch, or sometimes after several minutes of usage, with one instance reaching 22 minutes before closing.

Please note that the AdMob and GDPR implementation in the sample project is based directly on your official GitHub examples.

I hope this information assists you in your investigation. Please let me know if you require any further details.

Thank you for your time and assistance.

Sincerely,

[Bilan]

Dear Mobile Ads SDK Support Team,

Thank you for your response.

I have followed your instructions and uploaded the sample project that reproduces the issue via the Google Form link you provided.

As requested, here are the details:

App ID: ca-app-pub-3940256099942544~3419835254 (Default test ID)

Ad Unit ID: ca-app-pub-3940256099942544/6300978111 (Default Banner test ID)

Regarding the application's behavior:

The application runs stably on standard Android 15 (4KB page size) devices/emulators.

The application runs stably on standard Android 16 (4KB page size) devices/emulators.

The application also runs stably on Android 16 with a 16KB page size system image.

However, on the Android 15 (API 35) system image with a 16KB page size, the application closes unexpectedly by itself. This can happen immediately after launch, or sometimes after several minutes of usage, with one instance reaching 22 minutes before closing.

Please note that the AdMob and GDPR implementation in the sample project is based directly on your official GitHub examples.

I hope this information assists you in your investigation. Please let me know if you require any further details.

Thank you for your time and assistance.

Sincerely,

في Thursday, July 3, 2025 في تمام الساعة 4:21:59 PM UTC+1، كتب Mobile Ads SDK Forum Advisor رسالة نصها:

[Mobile Ads SDK Forum Advisor]

Hi Bilan,

I have executed our Sample project with the Test IDs in the Pixel 9 Pro emulator, Android 15 (API level 35) with a 16KB page size but unable to replicate the issue. 

Please note that we didn’t receive the files which you have shared. Could you kindly reshare the files using the link below. . 

If the file(s) you are looking to share are less than 25mb in total you can attach them to this case on your next reply. If you are having trouble attaching your file to this case or if your file(s) are larger than 25mb, you can share your files via reply to author option or by performing the following steps:

https://docs.google.com/forms/d/e/1FAIpQLSfkAiXMeYP-fw1W3Z-tT9uwmATEKO5X6S-th0gR2ezdKaaqfg/viewform?usp=pp_url&entry.400550049=Mobile+Ads+SDK&entry.460850823=500Ht00001rh7PAIAY&entry.80707362=00316952

2. Fill out all fields, and attach your file(s).

3. Please reply to this thread when you have uploaded your file(s). Please do not share this link.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-04 05:50:33Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rh7PA:ref" (ADR-00316952)

[Mobile Ads SDK Forum Advisor]

Hi Bilan,

I ran the provided sample clickCountTest in the mentioned environment Android 15 (API 35) system image with a 16KB page size and the application is neither closing by itself nor crashing during app launch or even after waiting for 22 minutes. As stated earlier that the reported issue is not replicating in Google BannerExample too. I have set up the Android Emulator with a 16-KB-based, Android 15 system image as well. Since the issue is not replicating can you please confirm if the reported issue is replicating in our Google BannerExample? If so, kindly share with us the below details for further investigation:

• Steps to reproduce the issue
• Device affected
• Charles logs

You can provide the following details via reply privately to the author option.

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-04 22:38:01Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rh7PA:ref" (ADR-00316952)

[Bilan]

Dear Mobile Ads SDK Support Team,

Thank you for your response.

I understand that the files from my previous submission were not received. I apologize for this issue.

To clarify, I initially submitted the sample project via the Google Form link you provided, and received a confirmation message stating:
"Google Ads Developer Support Form for Large Attachments - Thank you for submitting your attachments. Please reply back on your Google developer forum thread to let the support team know that you have uploaded your file(s)."

However, since the project still hasn't been received on your end, I am now providing the sample project that reproduces the issue via the following Google Drive link within this message:

Google Drive Project Link: https://drive.google.com/file/d/1Wmpa4FMMGVzZsdaH9Hd2ASiS7II9aCoa/view?usp=drive_link

As requested, here are the details:

App ID: ca-app-pub-3940256099942544~3419835254 (Default test ID)

Ad Unit ID: ca-app-pub-3940256099942544/6300978111 (Default Banner test ID)

Regarding the application's behavior and the environment where the crash occurs:

The application runs stably on standard Android 15 (4KB page size) devices/emulators.

The application runs stably on standard Android 16 (4KB page size) devices/emulators.

The application also runs stably on Android 16 with a 16KB page size system image.

However, on the Android 15 (API 35) system image with a 16KB page size (build fingerprint: google/sdk_gphone16k_x86_64/emu64xa16k:15/AE3A.240806.043/12960925:userdebug/dev-keys), the application closes unexpectedly by itself. This can happen immediately after launch, or sometimes after several minutes of usage, with one instance reaching 22 minutes before closing.

Please note that the AdMob and GDPR implementation in the sample project is based directly on your official GitHub examples.

I hope this re-submission via Google Drive and detailed information assists you in your investigation. Please let me know if you require any further details.

Thank you for your time and assistance.

Sincerely,

[Mobile Ads SDK Forum Advisor]

Hi Bilan,
As mentioned in the previous thread, could you please provide the following details for further investigation:

• Steps to reproduce the issue

• Charles logs
• Video recording of the issue reproduction

Thanks,
 

Mobile Ads SDK Team

Feedback
How was our support today?

               

[2025-07-08 00:15:07Z GMT] This message is in relation to case "ref:!00D1U01174p.!500Ht01rh7PA:ref" (ADR-00316952)

[hazel james]

Thanks for sharing the detailed breakdown — really helpful for others running into the same issue. From what you described, it definitely looks like the crash is tied to AdMob’s interaction with the WebView component under the Android 15 emulator with 16KB page size. Since it doesn’t reproduce on Android 16, it could be an emulator-specific bug or compatibility issue with that system image.

A couple of things you could try:

• Test on a physical device running Android 15 if possible, to confirm if this is only an emulator issue.

• Double-check if you’re on the latest Google Play Services beta — sometimes fixes land there first.

• Report this to the Google Ads SDK issue tracker with your tombstone logs, since it looks like a lower-level crash in the rendering pipeline.

For perspective, even large-scale apps like Spotify Premium rely on stable ad delivery and rendering (especially for free-tier users). Crashes like this could impact user trust quickly, so it’s great you’re isolating it early in testing.