Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2018.1.5f1
Issue ID
1051002
Regression
No
Running the game causes .NET 4.X crash without stack trace
How to reproduce:
1. Open user-submitted project (quantum_unity.zip)
2. Play QuantumMenu scene
3. Write "test" in username field and press "Connect"
4. Press "Create New Room"
5. Write" Test" in Room Name field and press Create
6. Within ~300 frames of simulation the editor (or player) will crash without any errors or log messages.
Expected result: Unity doesn't crash
Actual result: Unity crashes
Reproducible with: 2018.1.7f1, 2018.2.0b8
Not reproducible with: 2018.3.0a3
Could not test with: 2017.1, 2017.2, 2017.4 (Project is not compatible)
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [Android] Crash on startup when Depth Stencil Format is set to S8_UINT
- Multiple errors occur when setting the Render Object Event to AfterRenderingPostProcessing while using STP for Upscaling
- UnityYamlMerge.exe doesn't correctly handle merge conflicts in modified properties on a prefab variant
- Inconsistent color scheme in "Details" section of "Select Presets" inspector window
- Crash on __pthread_kill when launching Editor via command-line with "-disableManagedDebugger" argument
Add comment