Search Issue Tracker
Fixed in 3.0.6
Votes
0
Found in [Package]
3.0.5
Issue ID
1327921
Regression
No
Creating a new code file causes long stalls in SyncVS.PostprocessSyncProject - Rider
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 VS Code and Visual Studio
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
- TutorialManager Warnings are thrown when creating Test Track, LEGO or 2D Platform microgame template projects
- Incorrect ScrollToItem behavior when called on a deattached ListView
- Zooming in/out in Scene View window on the display the zoom takes place in does not work
- Changing Game View resolution when there are 2 Game View Windows on 2 different displays makes the view stretched
- Maximising Game view window on one display makes black bars appear on another display
Resolution Note (fix version 3.0.6):
Fixed in: JetBrains Rider Editor 3.0.6