Search Issue Tracker
Active
Under Consideration for 2022.3.X, 6000.0.X
Votes
7
Found in
2022.3.24f1
2023.2.17f1
6000.0.0b14
7000.0.0a1
Issue ID
UUM-69275
Regression
No
[Android][Vulkan] The Player crashes when running on specific Adreno GPU devices
Steps to reproduce:
1. Open the attached “VulkanCrashIssue-6000.0” project
2. Build and Run the project on the device
3. Wait for half a minute
Expected result: The Player doesn’t crash
Actual result: The Player crashes
Reproducible with: 2021.3.37f1, 2022.3.24f1, 2023.2.17f1, 6000.0.0b14
Could not test with: 2023.2.18f1 (red screen)
Testing environment: macOS Sonoma 14.3.1 (Intel)
Not reproducible on: No other environment tested
Reproducible with these devices:
VLNQA00513 - OnePlus Nord N10 5G (BE2029), CPU: Snapdragon 690 SM6350, GPU: Adreno 619, OS: 11
VLNQA00472 - samsung Galaxy A52 (SM-A525F), CPU: Snapdragon 720G (SM7125), GPU: Adreno 618, OS: 12 (freezes)
Xperia 10 III (SOG04) (by user)
AQUOS sense6 (SH-M19) (by user)
AQUOS sense7 (SH-53C) (by user)
Galaxy A52 5G (SC-53B) (by user)
Not reproducible with these devices:
VLNQA00334 - Xiaomi Mi A3 (Mi A3), CPU: Snapdragon 665 SM6125, GPU: Adreno 610, OS: 11
VLNQA00526 - samsung Galaxy A12 (SM-A125F), CPU: Mediatek MT6765 Helio P35 (12nm), GPU: PowerVR Rogue GE8320, OS: 12
VLNQA00409 - Galaxy Z Fold3 5G (SM-F926B), CPU: Snapdragon 888, GPU: Adreno 660, OS: 11
Note: Reproducible with Vulkan and with OpenGLES, but only with OnePlus Nord N10 5G, which seems to be a duplicate of another issue
The last few lines of the stacktrace:
2024/01/24 12:01:10.492 11289 Adreno-GSL <gsl_ldd_control:553>: ioctl fd 90 code 0xc040094a (IOCTL_KGSL_GPU_COMMAND) failed: errno 35 Resource deadlock would occur
2024/01/24 12:01:10.492 11289 Adreno-GSL <log_gpu_snapshot:462>: panel.gpuSnapshotPath is not set.not generating user snapshot
2024/01/24 12:01:10.584 11289 Adreno-GSL <sharedmem_gpuobj_alloc:2736>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
2024/01/24 12:01:10.584 11289 Adreno-GSL <gsl_memory_alloc_pure:2604>: GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed.
2024/01/24 12:01:10.586 11289 libc malloc(532480) failed: returning null pointer
2024/01/24 12:01:10.587 11289 libc++abi terminating with uncaught exception of type std::bad_alloc: std::bad_alloc
2024/01/24 12:01:10.587 11289 CRASH Forwarding signal 5
0001/01/01 00:00:00.000 -1 --------- beginning of crash
2024/01/24 12:01:10.587 11289 libc Fatal signal 5 (SIGTRAP), code 1 (TRAP_BRKPT), fault addr 0x7a1d6b9df0 in tid 11827 (UnityGfxDeviceW), pid 11289 (sue.vulkancrash)
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Errors "InvalidOperationException: Trying to use a texture (_InternalGradingLut)..." and “Render Graph Execution error” shown and Scene turns black when 16 or more Render Objects are used
- GameObjects in the Game View are rendered differently than in the Scene View when the Rendering Path is set to "Deferred" and Screen Space Shadows Renderer Feature is added
- Errors “InvalidOperationException: Trying to use a texture (_CameraDepthTexture)...” and “Render Graph Execution error” shown when selecting GameObjects with Mesh Renderer from the Hierarchy
- macOS stutters in a minimal project
- [Usability] HDRP Wizard calls for VR fixes when opening the HDRP Wizard a second time after they have already been applied and the Wizard has finished checking
raofr_msn
Aug 07, 2024 04:34
same issue in Samsung S20 Snapdragon 865
actopolus
Jun 25, 2024 14:45
Same issue Xiaomi Redmi 8A, 4GB, Adreno 505 (game occupied ~1.2GB).
When ads opened (chrome):
16417 16865 W Adreno-GSL: <sharedmem_gpuobj_alloc:2713>: sharedmem_gpumem_alloc: mmap failed errno 12 Out of memory
.....
17312 17312 E chromium: [17312:17312:20240625,162713/109828:ERROR process_memory_range/cc:75] read out of range
17312 17312 E chromium: [17312:17312:20240625,162713/110082:ERROR process_memory_range/cc:75] read out of range
...
06-25 16:27:13.199 16417 17250 E CRASH : Version '2022.3.20f1 (61c2feb0970d)', Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
...
16417 17250 E CRASH : pid: 16417, tid: 17250, name: RenderThread >>> packagename <<<
16417 17250 E CRASH : uid: 10249
16417 17250 E CRASH : signal 6 (SIGABRT), code -1 (SI_QUEUE), fault addr --------
16417 17250 E CRASH : r0 00000000 r1 00004362 r2 00000006 r3 64931b18
16417 17250 E CRASH : r4 64931b2c r5 64931b10 r6 00004021 r7 0000016b
16417 17250 E CRASH : r8 64931b28 r9 64931b18 r10 64931b48 r11 64931b38
16417 17250 E CRASH : ip 00004362 sp 64931ae8 lr b07e9d07 pc b07e9d1a
16417 17250 E CRASH :
16417 17250 E CRASH : backtrace:
16417 17250 E CRASH : #00 pc 0005ed1a \apex\comandroidruntime\lib\bionic\libcso (abort+166) (BuildId: 940109a4b687bf19a1c73c8c92365f8c)
16417 17250 E CRASH : #01 pc 00005a49 \system\lib\liblogso (__android_log_assert+176) (BuildId: c44a6fcfe562b3f8a3dca0e76e1af7aa)
16417 17250 E CRASH : #02 pc 001f6b8b \system\lib\libhwuiso (BuildId: 47d233df06f54edf127254bb2eccbd67)
16417 17250 E CRASH : #03 pc 001f5f15 \system\lib\libhwuiso (BuildId: 47d233df06f54edf127254bb2eccbd67)
16417 17250 E CRASH : #04 pc 001f5455 \system\lib\libhwuiso (BuildId: 47d233df06f54edf127254bb2eccbd67)
16417 17250 E CRASH : #05 pc 002029b9 \system\lib\libhwuiso (BuildId: 47d233df06f54edf127254bb2eccbd67)
16417 17250 E CRASH : #06 pc 00202811 \system\lib\libhwuiso (BuildId: 47d233df06f54edf127254bb2eccbd67)
16417 17250 E CRASH : #07 pc 0000d90b \system\lib\libutilsso (android::Thread::_threadLoop(void*)+214) (BuildId: 8d87721383c85120f02878beed96ee29)
16417 17250 E CRASH : #08 pc 000a69b7 \apex\comandroidruntime\lib\bionic\libcso (__pthread_start(void*)+20) (BuildId: 940109a4b687bf19a1c73c8c92365f8c)
16417 17250 E CRASH : #09 pc 000601af \apex\comandroidruntime\lib\bionic\libcso (__start_thread+30) (BuildId: 940109a4b687bf19a1c73c8c92365f8c)
Peter77
Apr 08, 2024 15:26
Related forum thread:
https://forum.unity.com/threads/in-72861-app-crashes-on-some-android-devices-which-has-adreno-619-gpu.1574122/