Search Issue Tracker
Won't Fix
Votes
0
Found in
2018.4
2018.4.19f1
2020.2
Issue ID
1243612
Regression
No
[Android] Mono Player Crash when calling System.Diagnostics.Process.GetCurrentProcess()
How to reproduce:
1. Open the attached "CrashReport.zip" Project
2. Build and run the "SampleScene" Scene to Android
Actual Behavior: The app crashes or freezes (On LTS)
Reproducible with: 2018.4.22f1, 2019.3.13f1, 2020.1.0b9, 2020.2.0a10
Devices reproduced:
VLNQA00015, Samsung Galaxy Note8 (SM-N950W), Android 8.0.0, CPU: Snapdragon 835 MSM8998, GPU: Adreno (TM) 540
VLNQA00285, Samsung Galaxy J4 Core (SM-J410F), Android 8.1.0, CPU: Snapdragon 425 MSM8917, GPU: Adreno (TM) 308
Note: The issue does not reproduce with IL2CPP. It also did not reproduce with iPhone so it might be related to 32bit architecture.
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
- Articulation Body with 'Revolute' Joint Type has erratic behavior when Upper Limit is set to above 360
- WebGL Player fails to render Scene when Terrain with Detail Mesh is added and WebGPU Graphics API is used
- Inconsistent errors are logged when different types are passed into the Query "Q<>" method in UIToolkit and the ancestor VisualElement is null
- Crash on GetMaterialPropertyByIndex when opening a specific Scene
- Discrepancies in the styling are present when using a TSS file instead of a USS file in custom EditorWindow
Resolution Note (2020.2.X):
Given that the issue is Mono only, the API is not frequently used and the games can only be shipped for Android using il2cpp, it's not worth spending time fixing this.