You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This bug has been fixed in the latest release of VS Code Insiders!
@wszgrcy, you can help us out by commenting /verified if things are now working as expected.
If things still don't seem right, please ensure you're on version ccdd214 of Insiders (today's or later - you can use Help: About in the command palette to check), and leave a comment letting us know what isn't working as expected.
Activity
wszgrcy commentedon Apr 5, 2025
on 1.98.2
jeanp413 commentedon Apr 6, 2025
This PR seems to be the reason #244144
cc @deepak1556
deepak1556 commentedon Apr 7, 2025
Yes this due to us creating a new service worker controller since the webview ID information is passed via the creation URL.
ER-95 commentedon Apr 9, 2025
What workarounds are there for the time being? VSCode is currently borderline unusable with this bug for me.
ER-95 commentedon Apr 11, 2025
Is there any update on how to work around this? Not using VSCode until the end of April is really not an option for me.
29 remaining items
deepak1556 commentedon May 19, 2025
#249114 should address this issue, if you can build vscode from source please help confirm if the loading perf is restored with the change. Thanks!
vs-code-engineering commentedon May 20, 2025
This bug has been fixed in the latest release of VS Code Insiders!
@wszgrcy, you can help us out by commenting
/verified
if things are now working as expected.If things still don't seem right, please ensure you're on version ccdd214 of Insiders (today's or later - you can use
Help: About
in the command palette to check), and leave a comment letting us know what isn't working as expected.Happy Coding!
wszgrcy commentedon May 20, 2025
/verified
dongwa commentedon May 21, 2025
When will the next official version be released?
gjsjohnmurray commentedon May 21, 2025
Early June - see #248627
vladstudio commentedon May 21, 2025
Seems to be already fixed in VSCode Insiders!