Search Issue Tracker
Fixed in 2018.3.X
Votes
0
Found in
2017.3.1f1
Issue ID
1052246
Regression
No
Unity crashes when debugging a string with an invalid Unicode character
How to reproduce:
1. Open the attached "1052246.zip" project
2. Open "main" scene and "BugRepro" script
3. Add a breakpoint in line 11
4. Attach the debugger to Unity Editor
5. Press the Play button in Unity
Expected result: Unity continues to run
Actual result: when the breakpoint is hit, Unity closes
Reproducible with - 2017.1.0a1, 2017.1.4p2, 2017.2.3p2, 2017.4.6f1, 2018.1.7f1, 2018.2.0b9, 2018.3.0a3
Notes:
- not related to a specific IDE. Reproducible with both Visual Studio and JetBrains Rider
- the crash does not occur if no additional characters are added to the string (to check this, uncomment line 10)
Fixed only in .NET 4.x
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- “Remove Unused Overrides” available on not loaded Scene and throws “ArgumentException: The scene is not loaded” warning
- Adaptive Probe Volume occlusion edge is calculated incorrectly when viewing probes near geometry edges
- Sampling a texture using an HLSL file throws shader errors and the code does not compile
- "Graphics.CopyTexture called with null source texture" error when Base Camera of an Overlay Camera is removed with DX11 Graphics API and Compatibility Mode enabled
- WebGL sends wrong value with large numbers when SendMessage function is used
Add comment