IssueTracker

Steps to reproduce the problem (including sample code if appropriate).

 when I used an app with the google maps sdk inside  on a GMS phone(it means the phone also built-in Google Maps application)

What happened

 An ANR occurred,and the phone system also crashed and restart.

What you think the correct behavior should be

ANR should not happened ,and the an app with the google maps sdk can also run well

Which device did you use to reproduce this issue?

  A customized Android 12 phone

Can you confirm if this issue is reproducible on a Pixel/Nexus device?

  i can't confirm that

Screen Record of the Issue

  i can't provider it due to it not an guaranted issue.

Bug logcat and ANR trace

you can choice the data/tlog/persist/persist_00000_240204_095014.log in the tar.gz

and you can get the anr trace in data/tlog/fatal/anr which also in the tar.gz

02-04 09:50:18.966   693   693 I tombstoned: received crash request for pid 6826
02-04 09:50:18.966   693   693 I tombstoned: found intercept fd 512 for pid 6826 and type kDebuggerdJavaBacktrace
02-04 09:50:18.966  6826  6831 I droid.apps.map: Wrote stack traces to tombstoned
02-04 09:50:18.967   693   693 W tombstoned: missing output fd
02-04 09:50:18.968  1549  8571 I system_server: libdebuggerd_client: done dumping process 6826
02-04 09:50:18.969  1549  8571 I ActivityManager: Done dumping
02-04 09:50:18.972  4217  4309 D nativeloader: Configuring clns-9 for other apk /data/app/~~-cKkKp1fklLggpmFvEUUsA==/com.google.android.gms-N5gOmy1saVdRCwRclvJzfw==/base.apk. target_sdk_version=34, uses_libraries=, library_path=/data/app/~~-cKkKp1fklLggpmFvEUUsA==/com.google.android.gms-N5gOmy1saVdRCwRclvJzfw==/lib/arm64:/data/app/~~-cKkKp1fklLggpmFvEUUsA==/com.google.android.gms-N5gOmy1saVdRCwRclvJzfw==/base.apk!/lib/arm64-v8a, permitted_path=/data:/mnt/expand:/data/user/0/com.google.android.gms
02-04 09:50:18.973  1549  8571 E ActivityManager: ANR in com.google.android.apps.maps
02-04 09:50:18.973  1549  8571 E ActivityManager: PID: 6826
02-04 09:50:18.973  1549  8571 E ActivityManager: Reason: Broadcast of Intent { act=android.intent.action.BOOT_COMPLETED flg=0x89000010 cmp=com.google.android.apps.maps/com.google.android.apps.gmm.locationsharing.reporting.RestartDetectionBroadcastReceiver (has extras) }
02-04 09:50:18.973  1549  8571 E ActivityManager: Frozen: false
02-04 09:50:18.973  1549  8571 E ActivityManager: Load: 0.0 / 0.0 / 0.0
02-04 09:50:18.973  1549  8571 E ActivityManager: ----- Output from /proc/pressure/memory -----
02-04 09:50:18.973  1549  8571 E ActivityManager: some avg10=0.10 avg60=0.36 avg300=0.13 total=701524
02-04 09:50:18.973  1549  8571 E ActivityManager: full avg10=0.00 avg60=0.01 avg300=0.00 total=96021
02-04 09:50:18.973  1549  8571 E ActivityManager: ----- End output from /proc/pressure/memory -----
......

My analysis

I think it due to the deadlock in the gms

Device info

Android 12   
GMS:[12_202304]
GMS's Maps apk: Maps_arm64.apk