Long startup activation time on the first start

[alexdevero]

🐛 Describe the bug
It takes significant amount of time to start the extension on first, fresh start of VS Code. This occurs only on the first start in the day. This leads to "Extension runner is unresponsive" error notification in VS Code. Any consequent startup activation time is at least 10x faster, ~950ms.

🌴 Visual Studio Code Version : 1.28.0-insider (system setup)
Commit: 2558a72d6902015b142ef45c57b664ce1f09e03f
🌴 Code Settings Sync Version : 3.1.2
🌴 Operating System : Win 10 Home (1803)
🌴 Occurs On: Start of VS Code
🌴 Proxy Enabled: No

📰 To Reproduce
Steps to reproduce the behavior:

1. Start fresh VS Code.
2. Open Running Extensions
3. Find Settings Sync
4. See error from VS Code

💪 Expected behavior
The first startup activation time should be similar to the consequent (~950ms).

📺 Console Error Log
First start:

Second start:

[shanalikhan]

Actually code is the same on first and second startup ...

What is really affecting the time might be the Visual Studio Code extension host.
Can you verify does it happens every time ~25900ms on the first startup of day ?

[alexdevero]

So far, I tested this three times and always with positive results -> ~25900ms.

[hibas123]

I can confirm this issue.

[IssueHuntBot]

@y-matsuwitter funded this issue with $40. Visit this issue on Issuehunt

[shanalikhan]

This issue is available for bounty. Fix and earn!

[IssueHuntBot]

@thejewdude has submitted a pull request. See it on IssueHunt

[shanalikhan]

@alexdevero this issue is fixed. let me know if you see such behavior

[IssueHuntBot]

@shanalikhan has rewarded $28.00 to @thejewdude. See it on IssueHunt

• 💰 Total deposit: $40.00
• 🎉 Repository reward(20%): $8.00
• 🔧 Service fee(10%): $4.00