Search Issue Tracker
Fixed in 1.2.4
Votes
0
Found in [Package]
1.2.3
Issue ID
1327922
Regression
No
Creating a new code file causes long stalls in SyncVS.PostprocessSyncProject - VSCode
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 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
- Crash on physx::shdfnd::atomicIncrement when adjusting values on a character controller component after entering Play mode in Prefab edit mode
- [Rendering Debugger] [NewInputSystem] Debug Overlays in Play mode throws InvalidOperationException when using New Input System
- [RenderingDebugger][InputSystemPackage] Ctrl+Backspace shortcut doesn't work to open the Rendering Debugger when New Input System is in use
- No option to skip video transcoding when launching a Project
- “ValidateSchema Error2” error is thrown in the Player when using IL2CPP Scripting Backend
Resolution Note (fix version 1.2.4):
Fixed in 1.2.4 available for 2019.2 and above