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
- “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