Search Issue Tracker
Fixed in 2018.2.X
Fixed in 2017.2.X, 2017.4.X, 2018.1.X
Votes
1
Found in
2017.2.0b1
2017.3.0b6
Issue ID
965024
Regression
Yes
[Android] Crash with signal 11 (SIGSEGV), code 1 when using try catch on Null value with performance reporting enabled
To reproduce:
1. Download and open attached "repro965024.zip" project.
2. Link the project to organization.
3. Activate performance reporting.
4. Build and run the project on any Android device.
Expected result: Application loads and try catch block executes.
Actual result: Application crashes after splash screen.
Reproduced with: 2018.1.0a5, 2017.3.0b10, 2017.2.0p2, 2017.2.0b1.
Not reproduced with: 2017.2.0a4, 2017.1.2p3.
Regression introduced in: 2017.2.0b1.
Devices Under Test:
Samsung SM G928F*, OS:7.0, CPU:arm64-v8a, GPU:Mali-T760,
Build:samsung/zenltexx/zenlte:7.0/NRD90M/G928FXXU3CQG2:user/release-keys
Lge LG H815 (G4)*, OS:6.0, CPU:arm64-v8a, GPU:Adreno (TM) 418,
Build:lge/p1_global_com/p1:6.0/MRA58K/1620215065b6f:user/release-keys
Google Pixel XL*, OS:8.0.0, CPU:arm64-v8a, GPU:Adreno (TM) 530,
Build:google/marlin/marlin:8.0.0/OPR6.170623.012/4283428:user/release-keys
Notes: Did not crash on iOS and Standalone. On iOS however, application starts in hidden mode, but can be opened correctly from the system tray. In 2018.1 application does not crash anymore, but black screen appears and application does not function.
Fixed in: 2017.2.2p3, 2017.4.4f1, 2018.1.2f1 and 2018.2.0a6
Comments (4)
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
- [Android][BiRP] Depth processing is handled incorrectly on certain Android devices when using 2 camera's
- [APV] Cancelling Display Dialog Error is thrown after Adaptive Probe Volumes tab is open in Lighting Window
- [APV] NullReferenceException is thrown when baking Adaptive Probe Volume for a Terrain with Non-GI Contributing Tree Prototypes and multiple APV objects with different LayerMasks are present on the scene
- Hands are not recognized when using Hololens 2
- "OnTriggerExit2D" is called before "OnTriggerEnter2D" when object is destroyed immediately
NaxiaLascif
Apr 16, 2019 22:40
EVALDAS_UNITY,
I have tried:
2017.2.1p1
2017.2.2f1
2017.3.1f1
And all versions of unity will sig-fault on a Try/Catch block :-(
ring3124
Jun 29, 2018 09:49
I'm using Unity2017.3.1p4 ,and it has the same problem. Will this be fixed in the after 2017.3.1 patch?
Evaldas_Unity
Jun 04, 2018 11:36
Fixed in: 2017.2.2p3, 2017.4.4f1, 2018.1.2f1 and 2018.2.0a6
nschrag_synapse
May 23, 2018 19:19
Will this be released in a 2018.1 build? If so, what's the timeline on that?