Search Issue Tracker
Fixed in 2020.1.X
Fixed in 2019.3.X
Votes
1
Found in
2019.2.0b10
2019.2.10f1
2019.3.0a11
2020.1
Issue ID
1195002
Regression
Yes
Unable to report crash bug when Script is still opened in Visual Studio
Reproduction steps:
1. Open project in "ForceCrash.zip"
2. In Project window open "ForceCrash.cs" using Microsoft Visual Studio 2019 and keep it open
3. Attach "ForceCrash.cs" to any GameObject
4. Enter Play Mode and Unity will crash
5. Try reporting a bug
Expected result: You are successfully able to report the issue using Bug reporter
Actual result: Upon clicking "Send", you encounter an error "...Error code: file read failed" and are not able to submit the bug
Reproducible with: 2019.2.11f1, 2019.3.0b8, 2020.1.0a11
Not reproducible with: 2017.4.33f1, 2018.4.12f1, 2019.2.0b9, 2019.3.0a10
Notes:
1. Bug seems to only reproduce when using MS Visual Studio (I tested with version 16.3.5, 16.3.7) and not the other editors (also tried Rider editor, Notepad, Sublime Text, WordPad, Visual Studio Code)
2. Could not reproduce the bug using Visual Studio on Mac OS
3. It does not seem to matter how you crash Unity (using Unity tools or recreating Active bugs)
4. During the bug reporting process, if you turn off MS Visual Studio, the issue does not reproduce anymore
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Missing Device Simulator API
- Shadow gets cut off when in Play Mode and using shader "Shader Graph/Rotation Shader" for material
- Unable to get textureOverrideSettings from BuildPipeline.GetBuildTargetName when trying to pass in the platform string
- Getting the current process name returns Null when building with IL2CPP
- Documentation page is not displayed for the user when he clicks on "Open Reference for SceneTemplateAsset" question mark
Add comment