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
1
Found in
5.5.0f3
Issue ID
859368
Regression
No
Stepping over a specific breakpoint while debugging in VS Code crashes editor
To reproduce:
1. Open attached project
2. Open 'MainScene' in project and run built game for Mac (we need 2 games would be played parallelly)
3. Open ‘InitialTurnScript’ in 'Scripts'->'Game'
4. Set a break point in the InitialTurnScript in the Update method on line 121 and start debugging
5. Create 2 users, choose the lowest timeout for game discovery
6. Press 'Step over' when you hit breakpoint
Expected: you will be able to continue debugging after clicking 'step over' button in VS Code
Actual: Unity crashes
Reproduced on: 5.5.0f3, p2, 5.6.0b1
NOTE: not able to reproduce on 5.4 and to strip project, because deleting or recompiling 'Library folder' (has the biggest weight) causes disability to reproduce issue because of lost project functionality.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Editor crashes on StoredGraphicsBuffer::GetGfxBufferID when VFX Graph property is modified during Play Mode and Application.targetFrameRate is used to limit FPS
- Crash on NVAPI_Thunk when changing Player resolution while HDR display is used and Direct3D12 is set as the graphics API
- Only one out of multiple cameras is shown in the Play Mode while HDR display is used and Direct3D12 is set as the graphics API
- The "Paste Component as New" option is incorrectly displayed as active despite the action being prohibited
- "TLS Allocator ALLOC_TEMP_TLS" errors are thrown when unsuccessfully importing an FBX file
Add comment