Search Issue Tracker
Duplicate
Votes
0
Found in
2018.3.0b4
Issue ID
1088856
Regression
No
[Android] App freezes/hangs instead of fatally crashing with Unhandled C# exceptions with Utils.ForceCrash()
Steps to reproduce:
1. Open QA attached project
2. Build & Run on Android device
3. Click the button to crash the application
4. Notice that the application freezes instead of crashing
Expected result: Game should fatally crash
Actual result: Game freezes
Reproduced in: 2019.1.0a4, 2018.3.0b4, 2018.3.0b1
Tested and reproduced devices with Mono and IL2CPP builds:
VLNQA00093, Samsung Galaxy S6 edge (SM-G925F), Android 7.0, CPU: Exynos 7 Octa 7420, GPU: Mali-T760
VLNQA00051, Xiaomi MI MAX (MI MAX), Android 6.0.1, CPU: Snapdragon 617 MSM8952, GPU: Adreno (TM) 510
VLNQA00153, Google Pixel XL (Pixel XL), Android 8.0.0, CPU: Snapdragon 821 MSM8996 Pro, GPU: Adreno (TM) 530
Does not reproduce testing on: Windows player
-
Resolution Note:
Issue is a duplicate of another issue which is now fixed and being backported to previously released Unity versions.
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
- Error “Shader error in 'YSCloudCover': call to 'tex3D' is ambiguous at Assets/YSCloudCoverText.shader(606) (on d3d11)“ is present when compiling tex3D shader with DXC
- Placeholder asset is not loaded with Advertisement Legacy sample when using the latest version of the package
- Addressables content build fails but the Player build is successful when building a development build
- Out-of-bounds memory access with multiple CanvasRenderers under a Canvas when using Mesh API
- Inspector tries to access file after it was deleted when the file was locked in Inspector window
This is a duplicate of issue #1142726