Search Issue Tracker

Fixed in 2022.1.X

Fixed in 2019.4.X, 2020.3.X, 2021.2.X

Votes

6

Found in

2020.3.17f1

2021.1

Issue ID

1374806

Regression

Yes

[Android] Crashes with signal 6 (SIGABRT)' error and 'JNI ERROR' abort message on some devices running Android 8 or lower

Android

-

How to reproduce:
1. Open the attached project "InternalProject"
2. Build And Run on Android device

Expected results: The app does not crash
Actual results: The app crashes

Reproducible with: 2020.3.17f1, 2020.3.21f1, 2021.1.27f1
Not reproducible with: 2020.3.16f1
Could not test with: 2019.4.32f1 (script compile errors), 2021.2.0f1, 2022.1.0a14 ('AmbiguousMatchException: Ambiguous match found' error)

Reproducible on:
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00052, Xiaomi MI MAX (MI MAX), Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00109 - Xiaomi Mi Note Pro (MI NOTE Pro), OS: 7.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno 430
VLNQA00176, Xiaomi Redmi 4 (Redmi 4), Android 6.0.1, CPU: Snapdragon 430 MSM8937, GPU: Adreno (TM) 505
----------, Huawei - (ELS-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G76

Not reproducible on:
VLNQA00288, Samsung Galaxy J7 (SM-J730F), Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00001, Google Pixel 2 (Pixel 2), Android 11, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
VLNQA00225, Qualcomm null (SDM845 for arm64), Android 8.1.0, CPU: Snapdragon 845 SDM845, GPU: Adreno (TM) 630
VLNQA00022, Xiaomi Redmi Note 3 (Redmi Note 3), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00109 - Xiaomi Mi Note Pro (MI NOTE Pro), OS: 7.0.0, CPU: Snapdragon 810 MSM8994, GPU: Adreno 430
VLNQA00034 - Google Nexus 4 (mako), OS: 5.1.1, CPU: Snapdragon S4 Pro APQ8064, GPU: Adreno 320
N/A, Huawei - (NOH-NX9), Android 10, CPU: NOT FOUND, GPU: Mali-G78

  1. Resolution Note (fix version 2022.1):

    Fixed in: 2022.2.0a3

Comments (1)

  1. xmarleauFFG

    Feb 09, 2022 02:27

    Could we know in which versions this issue got fixed? I'm not sure what version to get since all of them is .X

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.