Search Issue Tracker
Fixed
Votes
0
Found in
5.6.1f1
Issue ID
923028
Regression
No
Unity performance decreases when debugging and stepping over code instead of pressing Continue
Reproduction steps:
1. Open project attached (ReproProject.zip)
2. Open scene "MainScene" from Assets/Scenes
3. Open script PerformWork, add a breakpoint to line 13 and attach it to Unity.
4. Press play.
5. Press button "Do a single item of work".
6. Press continue in VS debugger.
7. Press button "Do a single item of work" again.
8. Press "Step over" (F10) twice.
Expected result: Unity performance will remain stable.
Actual result: CPU usage increases by every action Unity makes.
Reproduced on: 5.5.0f3, 5.6.0f3, 5.6.1p4, 2017.1.0b10 with VS2015 and VS2017.
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- Unity Cloud icon does not appear next to project and does not connect correctly when the project is created with Cloud but closed right after creation
- ScrollerSlider in the Scroller Control is still using UXMLTraits
- Crash on ExtractHandles when shutting down the Editor in a specific scene while Burst jobs are in progress
- Unity Hub closes with no "Project is currently open" window when selecting an already open project from the Projects list
- The Hub freezes indefinitely when copy/pasting a lot of characters in the “Set project display name” Hub window since it has no character limit
Add comment