-
Notifications
You must be signed in to change notification settings - Fork 29.8k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Workbench takes significantly longer than usual to become ready in Insiders #132086
Comments
Data from running System Info
Performance Marks
Extension Activation Stats
Raw Perf Marks: main
Raw Perf Marks: renderer
Raw Perf Marks: localExtHost
Node Cached Data Statscached data usedcached data missedcached data rejectedcached data created (lazy, might need refreshes) |
Is there a particular file you see this issue with or opening any workspace ? |
I had a file in the vscode-jupyter repo open, but it seems that any file will do. E.g. here's the --prof-startup output when starting Insiders with the vscode repo open to this file: https://github.com/microsoft/vscode/blob/main/src/vs/workbench/browser/parts/editor/editor.ts System Info
Performance Marks
Extension Activation Stats
Raw Perf Marks: main
Raw Perf Marks: renderer
Raw Perf Marks: workerExtHost
Raw Perf Marks: localExtHost
Node Cached Data Statscached data usedcached data missedcached data rejectedcached data created (lazy, might need refreshes) |
@joyceerhl Do you have by any chance the minimap enabled? Does this reproduce when closing all instances and launching with I noticed that a method called So my immediate reaction is that something is very very wrong on your computer around using @deepak1556 I think we did an Electron update in Insiders, maybe some change came in around GPUs? |
After discussions in stand up we decided to defer it to September as it is not yet clear. |
@joyceerhl can you follow the steps below to get a trace from the runtime,
Can you also confirm what is your display resolution and scaling. |
If I start Insiders with |
@joyceerhl can you please provide the data for #132086 (comment), otherwise this issue will eventually be closed with no action. Thanks! |
Apologies for the delay, here are the log files: Display resolution: 3240 x 2160 (recommended setting) |
Minor update, I don't have the root cause yet but all the GL driver calls are slow in the insiders version even the initialization one (100ms vs 1s) on your device. Once the main branch is open again, I will publish newer runtime builds that has GL tracing enabled to get better insight via --enable-gpu-service-logging |
Looking at the output from running with
--prof-startup
flag, restoring and resolving open editors in Insiders appears to take 30 seconds. In VS Code Stable the same step takes 5 seconds.logs.zip
System Info
Performance Marks
Extension Activation Stats
Raw Perf Marks: main
Raw Perf Marks: renderer
Raw Perf Marks: workerExtHost
Raw Perf Marks: localExtHost
Node Cached Data Stats
cached data used
cached data missed
cached data rejected
cached data created (lazy, might need refreshes)
The text was updated successfully, but these errors were encountered: