Search Issue Tracker

Fixed in 2021.2.X

Fixed in 2019.4.X, 2020.3.X, 2021.1.X

Votes

0

Found in

2019.4.15f1

2019.4.19f1

Issue ID

1315010

Regression

Yes

[Android] Signal 11 gets called instead of Signal 9 when using Application.Quit();

Mobile

-

How to reproduce:
1. Open the attached project "CrashTest.zip"
2. Build and Run the project to an Android device
3. Start recording a Logcat for the device
4. In the application click the top left "Test" button
5. Stop and check the Logcat recording

Expected result: Application exits with the following message "Process X exited due to signal 9 (Killed)"
Actual result: Application exits with "Process X exited due to signal 9 (Killed)" and "Process X exited due to signal 11 (Segmentation fault)" messages

Reproducible with: 2019.4.15f1, 2019.4.23f1
Not reproducible with: 2018.4.32f1, 2019.4.14f1, 2020.2.6f1, 2021.1.0b9, 2021.2.0a7

Reproducible on:
VLNQA00333, Hmd Global Nokia 7 plus, Android 10, CPU: Snapdragon 660, GPU: Adreno (TM) 512
VLNQA00099, Google Pixel XL, Android 9, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
VLNQA00321, Xiaomi MI 9 (MI 9), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00122, Samsung Galaxy S9 (SM-G960F), Android 10, CPU: NOT FOUND, GPU: Mali-G72
N/A, Samsung Galaxy S9 (SM-G960F), Android 8.0.0, CPU: Exynos 9 Series 9810, GPU: Mali-G72
VLNQA00318, Oneplus 7Pro (GM1913), Android 10, CPU: Snapdragon 855 SM8150, GPU: Adreno (TM) 640
VLNQA00231, Huawei HUAWEI Mate 20 Pro (LYA-L29), Android 9, CPU: HiSilicon Kirin 980, GPU: Mali-G76
VLNQA00316, Samsung Galaxy Note10 (SM-N970F), Android 9, CPU: Exynos 9 Series 9825, GPU: Mali-G76
X, Motorola Moto G8, X, CPU: Snapdragon 665, GPU: Adreno (TM) 610 (according to the user)
Not reproducible on:
VLNQA00288, Samsung Galaxy J7, Android 8.1.0, CPU: Exynos 7 Octa 7870, GPU: Mali-T830
VLNQA00332, Samsung Galaxy XCover4, Android 9, CPU: Exynos 7 Quad 7570, GPU: Mali-T720
VLNQA00052, Xiaomi MI MAX, Android 7.0, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00004, Meizu MX5, Android 5.0.1, CPU: MediaTek Helio X10 MT6795T, GPU: PowerVR Rogue G6200
N/A, LG V50 ThinQ 5G (LMM-V500N), Android 10, CPU: Qualcomm Snapdragon 855 (SM8150), GPU: Adreno 640
N/A, Samsung Galaxy S10 (SM-G975F), Android 10, CPU: Exynos 9820 (ARMv8), GPU: Mali-G76
N/A, Samsung Galaxy S9 (SM-G960F), Android 8, CPU: Exynos 9810 (ARMv8-A), GPU: Mali-G72
N/A, BlackShark 3 (KLE-H0), Android 10, CPU: Qualcomm Klein (ARM64-v8), GPU: Andreno 650
VLNQA00013, Samsung Galaxy S6 Edge Plus (SM-G928F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
N/A, Nokia 4.2 (TA-1157), Android 10, CPU: Qualcomm Snapdragon 439, GPU: Adreno 505

Notes:
- Clicking "Test" runs Application.Quit();

Comments (1)

  1. 6e87a046c43c0ffafe0b79e025e2e337?d=mm

    toptracer-emilio

    May 20, 2021 15:00

    Thank you for fixing this issue - when might we expect for it to be integrated into 2020.3?

    All the best,
    Emilio

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.