How to reproduce:
1. Open the attached project "IN-131391"
2. Build and run for Android
3. Observe the device screen

Actual result: App gets stuck on flickering Unity Slash Screen and after ~1 minute, the app crashes
Expected result: White square spinning is rendered

Reproducible with: 6000.0.6f1, 6000.0.66f1, 6000.3.6f1, 6000.4.0b6 (7e0f7195b8da), 6000.5.0a5
Could not test with: 2023.1.0a10 (Project gets stuck on "Initial Asset Database Refresh"), 6000.0.0b11 (a707ca4efec4) (Project crashes when building)

Reproducible on environment: macOS 26.2 (M1 Max)
Not reproducible on environment: No other environments tested

Reproducible with these devices:
VLNQA00531 - OnePlus OnePlus 11 5G (CPH2449), CPU: Snapdragon 8 Gen 2 (SM8550), GPU: Adreno 740, OS: 13
VLNQA00521 - Galaxy S22 Ultra USA (SM-S908U), CPU: Snapdragon 8 Gen 1 (SM8450), GPU: Adreno 730, OS: 14

Not reproducible with these devices:
VLNQA00232 - iPhone 8 Plus (MQ8M2ET/A), CPU: Apple A11 Bionic, GPU: Apple designed, OS: 16.7.10
VLNQA00403 - Galaxy Z Flip3 5G (SM-F711B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
VLNQA00655 - Samsung Galaxy A15 5G (SM-A156E), CPU: -, GPU: Mali-G57 MC2, OS: 15
VLNQA00422 - Galaxy S21 Ultra 5G (SM-G998B), CPU: Exynos 2100, GPU: Mali-G78, OS: 11

Notes:
- Does not reproduce in the editor
- Does not reproduce if the URP configuration assets are deleted/recreated
- The app crashes due to running out of memory based on logcat logs ({{The process has exhausted 256M for size class 65552}}, {{libc++abi terminating due to uncaught exception of type std::bad_alloc: std::bad_alloc}})
- Could not find stack trace, attached logcat logs “Logcat logs”