Search Issue Tracker

Fixed in 2018.3.7f1

Fixed in 2017.4, 2018.3, 2019.1

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

-

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 (9)

  1. Dcbe909f580514745e971cd99363ffa9?d=mm

    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.

  2. 30303a151bf1bac59ad9b3937b31a011?d=mm

    OleSviper

    Oct 21, 2019 14:05

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

  3. 2aa5b6594fae57333b32906f7da1e78d?d=mm

    umairmunawarsabasoft

    Oct 18, 2019 22:00

    Not resolved. Happening in Unity 2019.2.3f1.

  4. 469707f8d8fa950f138d1be133a64e2a?d=mm

    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'

  5. 38e952e1a13eeae323d47a933647244a?d=mm

    Interfeisovich

    Aug 16, 2019 07:02

    bug not fixed in 2018.4.4f

  6. Ebd80d22877ceac6f5843ef99b2e0819?d=mm

    Petr777

    Aug 15, 2019 08:10

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

  7. F5321276dee0d11ab1b8fdad4e78404e?d=mm

    PalashBansal96

    Mar 23, 2019 07:05

    Is this fixed in any of the 2018.3.x releases?

  8. F89eb78478973ff889243246f95e3a48?d=mm

    caret_games

    Feb 15, 2019 04:55

    Unity2017.2.0p5, Unity2017.2.2p1, Unity2017.2.4p1, ...

    In most unity2017.2, the same issues are causing memory leaks and crashes.

  9. F89eb78478973ff889243246f95e3a48?d=mm

    caret_games

    Feb 15, 2019 04:51

    Unity2017.2.0p5, Unity2017.2.2p1, Unity2017.2.4p1, ...

    In most unity2017.2, the same issue will lead to memory leaks and crashes.

Add comment

Log in to post comment

All about bugs

View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.