Search Issue Tracker
Won't Fix
Votes
0
Found in
2017.4.26f1
2017.4.31f1
Issue ID
1172795
Regression
No
[Android] When launching a thread on an Android device after calling Application.Quit() a crash is reported in logcat
To reproduce:
1. Open the attached project
2. Make sure the Scripting Runtime Version is set to .NET 4.6 and Mono is selected
3. Make sure the build is not a Development Build
4. Build and Run on Android device
5. Tap the big "Quit" button
6. Observe the logcat
Expected result: Application quits
Actual result: Application crashes
Reproduced with: 2017.4.31f1
Not reproduced with: 2018.4.5f1, 2019.1.13f1, 2019.2.0f1, 2019.3.0a11
Tested and reproduced with devices:
Google Pixel 2 XL 9 Snapdragon 835 MSM8998 Adreno (TM) 540 OpenGL ES 3.2
Oneplus OnePlus6T 9 Snapdragon 845 SDM845 Adreno (TM) 630 OpenGL ES 3.2
Samsung Galaxy S8 8.0.0 Exynos 9 Octa 8895 Mali-G71 OpenGL ES 3.2
Samsung Galaxy S9 9 Snapdragon 845 SDM845 Adreno (TM) 630 OpenGL ES 3.2
Xiaomi Mi 5 7.0 Snapdragon 820 MSM8996 Adreno (TM) 530 OpenGL ES 3.2
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
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Resolution Note (2019.3.X):
We will not be investigating and backporting a fix for this to 2017.x. The new scripting runtime was experimental for 2017.x. Please use 2018.x or newer where this issue doesn't exist.