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
- [UIBuilder] Changes aren't detected on types implementing IList
- [HDRP] Text is rendered with artefacts when using STP and resolution scale is set a float value
- [Settings Search] Search results not matching search term correctly
- Crash on memcpy when opening a project that loads TSS files
- Multiple errors appear when compiling a ShaderGraph shader's code in a specific project
Add comment