Search Issue Tracker
Fixed in 2019.1.X
Fixed in 2018.3.X
Votes
0
Found in
2018.3.0b2
2018.3.0b8
Issue ID
1096820
Regression
Yes
Unity crashes on Visual Studio debugger when there is a breakpoint on a SingletonWriter line which gets a ref value
How to reproduce:
1. Download, extract and open user's attached project (Crash on Ref.zip)
2. Open "MyScripty" script from the project window
3. Insert a breakpoint on line "var val = writer.InspectMe;" (there is an explanatory comment next to this line)
4. Start debugging (F5)
5. Return to Unity and go into play mode
-- watch the crash occur
Reproduces in: 2018.3.0b2, 2018.3.0b10, 2019.1.0a9
Does not reproduce in: 2018.3.0a1, 2018.3.0b1
Note: Not available for tesing in 2018.2 due to compile errors of the script.
Fixed in: 2018.3.0b11, 2019.1.0a10
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- The Scene View becomes gray and "NullReferenceException" errors are thrown when attaching the Unity Editor process to RenderDoc
- Memory usage rapidly rises when changing colors in the color wheel
- Physically Based Sky's Horizon and Zenith Tint Color Selection Bars don't have immediate access to color pickers
- EmptyAdditionalLightShadowmapTexture leaks from memory when URP quality level is changed using QualitySettings.SetQualityLevel
- Referenced ScriptableObject field does not get updated and cannot be set to "None" when there are no Objects of that type
Add comment