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

Please upgrade the underlying and chromium engine as well all Electron version atleast in vscode insiders #184257

Closed
fisforfaheem opened this issue Jun 3, 2023 · 4 comments
Closed

Please upgrade the underlying and chromium engine as well all Electron version atleast in vscode insiders #184257

fisforfaheem opened this issue Jun 3, 2023 · 4 comments
Assignees
@bpasero
Labels
*duplicate Issue identified as a duplicate of another issue(s) triage-needed

Comments

@fisforfaheem
Copy link

This will improve the speed, and performance and reliability.

here are the current details of VS CODE: Version: 1.79.0-insider (Universal)
Commit: 506cd50
Date: 2023-06-02T20:40:50.615Z
Electron: 22.5.5
Chromium: 108.0.5359.215
Node.js: 16.17.1
V8: 10.8.168.25-electron.0
OS: Darwin x64 20.6.0

and here is the latest stable versions:

image
@fisforfaheem
Copy link
Author

The use of a newer version of Chromium, which is more efficient than older versions.
The use of a newer version of Node.js, which is more efficient than older versions.
A number of performance optimizations that have been made to the Electron framework.

@fisforfaheem fisforfaheem changed the title Please upgrade the underlying NODE, and chromium engine as well all Electron version atleast in vscode insiders Please upgrade the underlying and chromium engine as well all Electron version atleast in vscode insiders Jun 3, 2023
@bpasero bpasero added the *duplicate Issue identified as a duplicate of another issue(s) label Jun 4, 2023
@vscodenpa
Copy link

Thanks for creating this issue! We figured it's covering the same as another one we already have. Thus, we closed this one as a duplicate. You can search for similar existing issues. See also our issue reporting guidelines.

Happy Coding!

@vscodenpa vscodenpa closed this as not planned Won't fix, can't repro, duplicate, stale Jun 4, 2023
@fisforfaheem
Copy link
Author

Please link the existing issue as well

@gjsjohnmurray
Copy link
Contributor

A search for 'electron' found this likely candidate on the first page:

#184021

@github-actions github-actions bot locked and limited conversation to collaborators Jul 19, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@bpasero bpasero

Labels
*duplicate Issue identified as a duplicate of another issue(s) triage-needed
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@bpasero @gjsjohnmurray @fisforfaheem @vscodenpa