Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Failed to execute 'importScripts' on 'WorkerGlobalScope' error while fetching scripts from extension #233060

Open
pankajk07 opened this issue Nov 5, 2024 · 4 comments · May be fixed by #233175
Open

Failed to execute 'importScripts' on 'WorkerGlobalScope' error while fetching scripts from extension #233060

pankajk07 opened this issue Nov 5, 2024 · 4 comments · May be fixed by #233175
Assignees
@deepak1556
Labels
bug Issue identified by VS Code Team member as probable bug electron Issues and items related to Electron electron-32-update extensions Issues concerning extensions network Network related issues upstream-issue-linked This is an upstream issue that has been reported upstream
Milestone
November 2024

Comments

@pankajk07
Copy link

Does this issue occur when all extensions are disabled?: Yes/No

  • VS Code Version: 1.95.1
  • OS Version: MacOS 14.6.1 (23G93)

Steps to Reproduce:

  1. Open Postman VS Code extension (in logged in state)
  2. Send a request to www.google.com
  3. Notice the response is not formatted
  4. Open developers tool
  5. Notice the following error
    Image

This was working in the previous release (1.94) but started failing from this release. On further investigation, it appeares that the new version has Chrome v128. This seems to be an issue in the said Chrome version as evident from here https://issues.chromium.org/issues/356827071
@mjbvz mjbvz assigned deepak1556 and unassigned mjbvz Nov 5, 2024
@pankajk07 pankajk07 mentioned this issue Nov 6, 2024
Open
1 task
@pankajk07
Copy link
Author

@deepak1556 Any updates on this. This issue is affecting the core feature of the extension. Can we please expedite it.

@pankajk07
Copy link
Author

pankajk07 commented Nov 6, 2024 •
edited
Loading

@deepak1556 The workaround shared by Electron team electron/electron#43556 (comment)

@deepak1556
Copy link
Collaborator

You can use the feature flag when launching vscode --disable-features=PlzDedicatedWorker and it should be respected.

@deepak1556 deepak1556 added bug Issue identified by VS Code Team member as probable bug extensions Issues concerning extensions electron Issues and items related to Electron upstream-issue-linked This is an upstream issue that has been reported upstream network Network related issues labels Nov 6, 2024
@deepak1556 deepak1556 added this to the November 2024 milestone Nov 6, 2024
@pankajk07 pankajk07 linked a pull request Nov 6, 2024 that will close this issue
Open
@pankajk07
Copy link
Author

@deepak1556 I have opened a PR for this. Feel free to leverage it if it makes sense

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@deepak1556 deepak1556

Labels
bug Issue identified by VS Code Team member as probable bug electron Issues and items related to Electron electron-32-update extensions Issues concerning extensions network Network related issues upstream-issue-linked This is an upstream issue that has been reported upstream
Projects
None yet
Milestone
November 2024
Development

Successfully merging a pull request may close this issue.

fix: disabled PlzDedicatedWorker in Electron pankajk07/vscode
3 participants
@deepak1556 @mjbvz @pankajk07