Search Issue Tracker
Fixed in 2.0.8
Votes
0
Found in [Package]
2018.4
2019.4
2020.2
2020.2.4f1
2021.1
2021.2
Issue ID
1315477
Regression
No
Creating a new code file causes long stalls in SyncVS.PostprocessSyncProject - Visual Studio
How to reproduce:
1. Open any Unity project or create a new one
2. Open Window>Analysis>Profiler
3. Set it to profile Editor instead of Playmode and start recording
4. Create a new script
5. Inspect the spike in CPU Usage
Expected results: Creating a new code file doesn't take as long
Actual results: Creating a code file stalls the Editor and the stall increases with the size of the project
Reproducible with: 2018.4.32f1, 2019.4.21f1, 2020.2.6f1, 2021.1.0b7, 2021.2.0a6
Notes:
1. In 2018.4 instead of SyncVS.PostprocessSyncProject taking a lot of time it's AssetPostProcessingInternal.PostprocessAllAssets()
2. Reproduces when creating any new file that contains code (.cs, .txt and etc.)
3. Reproduces with Rider and VS
-
Black_six
Jul 29, 2023 09:43
This problem was reproduced in 2021.3, rider plugin 3.0.17, and the problem was solved after upgrading the plugin to the latest 3.0.24
Add comment
All about bugs
View bugs we have successfully reproduced, and vote for the bugs you want to see fixed most urgently.
Latest issues
- [HDRP] Game view renders artifacts when Camera's Component "Post Anti-aliasing" is set to "TAA" and Dynamic Resolution's "Forced Screen Percentage" is changed
- A deactivated Prefab's name color becomes white when a GameObject in the scene is deactivated
- The Game view becomes blank when using Frame Debugger with MSAA and Texture binding enabled in Play Mode
- Crash on dynamixel_sdk.dynamixel:groupSyncReadTxRxPacket when entering Play Mode after updating path to Dynamixel SDK in script
- NullReferenceException is thrown when changing the Inspector preview selection
Resolution Note (fix version 2.0.8):
Fixed in Packages:
Visual Studio: 2.0.8
Rider: 3.0.6
VSCode: 1.2.4