Search Issue Tracker
Postponed means that the issue was either a feature request or something that requires major refactoring on our side. Since that makes the issue not actionable in the close future we choose to close it as Postponed and add it on our internal roadmaps and technical debt pages instead.
Postponed
Votes
0
Found in
5.4.0b6
Issue ID
770295
Regression
No
[VSTU] MultiThread debuging crashes editor
Steps to reproduce:
1. Download and open project "ThreadsBug"
2. Open Main scene
3. Open MultiThread.cs with Visual Studio
4. Attach VS to Unity process (with Attach To Unity button)
5. Put breakpoint inside while cycle
6. Start game from unity
7. When breakpoint hits in Visual studio keep clicking F10 (Step Over)
Notice Unity stops responding and closes (crashes).
Expected result:
Debugging without problems.
Actual result:
Unity crashes without displaying error message. An unhanded win32 exception occurred in Unity.exe [9448]. Look at "CrashDetails.xml" for more details.
Reproduced in: 5.2.2p4, 5.3.2p3, 5.4.0b6
-------------------------------------
Caused by issue on VSTU side
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
Add comment