Unity Issue Tracker - [Android] Crash with "GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed" on Adreno GPU devices

Fixed in 2018.3.7f1

Fixed in 2017.4.X, 2018.3.X, 2018.4.X, 2019.1.X

Votes

1

Found in

2018.3.0f2

Issue ID

1111097

Regression

Yes

[Android] Crash with "GSL MEM ERROR: kgsl_sharedmem_alloc ioctl failed" on Adreno GPU devices

Mobile

Dec 19, 2018

Steps to reproduce:
1. Open user attached project
2. Make a development build and run it on Android device
3. If the game starts continue to the second screen with a play button that also shows some currencies at the top left.
4. Press with 4 fingers on the screen to show the cheats.
5. Goto: World > Load Environment
- Memory leaks at this point following with a crash

Expected result: memory issues should not occur on

Reproduced in: 2019.1.0a12, 2018.3.0f2

Tested devices:
Reproduced on:
VLNQA00229, Oneplus OnePlus6T (ONEPLUS A6013), Android 9, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00118, Google Pixel 2 XL (Pixel 2 XL), Android 8.1.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00017, Huawei Nexus 6P (Nexus 6P), Android 8.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno (TM) 430
VLNQA00101, Samsung Galaxy Note8 (SM-N950U), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
No repro on:
VLNQA00224, Samsung Galaxy A5(2017) (SM-A520F), Android 8.0.0, CPU: Exynos 7 Octa 7880, GPU: Mali-T830
VLNQA00096, Samsung Galaxy S8 (SM-G950F), Android 8.0.0, CPU: Exynos 9 Octa 8895, GPU: Mali-G71
VLNQA00006, Samsung Galaxy S7 (SM-G930F), Android 8.0.0, CPU: Exynos 8 Octa 8890, GPU: Mali-T880

Comments (13)

scritchy

Sep 13, 2020 08:05

not fixed. 2019.3.13
Galaxy Tab A 8.0
Galaxy J3(2016)

libc.memcpy (memcpy:108)
libgsl.ioctl_kgsl_sharedmem_write (ioctl_kgsl_sharedmem_write:108)
libRBGLESv2_adreno.rb_vbo_cache_buffer (rb_vbo_cache_buffer:1366)
libRBGLESv2_adreno.cache_vbo_attrib (cache_vbo_attrib:342)
libRBGLESv2_adreno.0x5d385
libRBGLESv2_adreno.core_glDrawElementsInstancedXXX (core_glDrawElementsInstancedXXX:154)
libRBGLESv2_adreno.core_glDrawElements (core_glDrawElements:10)
libRBGLESv2_adreno.glDrawElements (glDrawElements:28)
libunity.0x25fa4c
libunity.0x376438
libunity.0x26588c
libunity.0x13f6dd
libunity.0x369a18
libunity.0x3d2380
libunity.0x369048
libunity.0x36aa10
libunity.0x36ba34
libunity.0x362038
libunity.0x32ca54
libunity.0x32dee4
libunity.0x33b5ec
libunity.0x1870c9
libunity.0x184b07
libunity.0x184b23
libunity.0x184cb7
libunity.0x232b85
libunity.0x2409a5
base.0xa39461
Olivier_Immersive

Jun 25, 2020 08:37

Reproduced with Unity 2019.3.7f1
ceceomer

Jun 20, 2020 02:01

It is still exist. Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
unity_ESPpfKWcV64y3Q

Apr 25, 2020 02:28

still exists in 2019.2.0-2019.3.11. only android il2cpp armv7a, arm64 is fine.
coffeecato

Nov 01, 2019 06:55

Still exists in Unity2018.4.1f.Mostly happens on Samsung devices, such as SM J610G, SM J610F, SM J415G, SM J415F, SM J610FN.
OleSviper

Oct 21, 2019 14:05

Still exists in Unity2019.2.9, for example on Samsung Galaxy J4 and J6+
umairmunawarsabasoft

Oct 18, 2019 22:00

Not resolved. Happening in Unity 2019.2.3f1.
Qbit86

Aug 16, 2019 07:40

Still reproduces in 2018.4.4f1: “at libRBGLESv2_adreno.rb_mempool2_alloc_pure(rb_mempool2_alloc_pure:417)”

signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0000002c
*** *** *** *** *** *** *** *** *** *** *** *** *** *** *** ***
Build type 'Release', Scripting Backend 'il2cpp', CPU 'armeabi-v7a'
Build fingerprint: 'samsung/gta2sltedx/gta2slte:8.1.0/M1AJQ/T385DXU3BSE3:user/release-keys'
Interfeisovich

Aug 16, 2019 07:02

bug not fixed in 2018.4.4f
Petr777

Aug 15, 2019 08:10

Looks like this bug exists in 2018.4.4f1 (not fixed)