Problems with Intel evo laptop and visual studio code (version 1.82). Any advice?

Question

1.00/5 (1 vote)

See more:

Hi everyone,

I’m encountering some issues with my Intel Evo laptop when using Visual Studio Code, and I’d appreciate any advice or insights from those who might have faced similar situations.

Here are the specifics of my setup:

Intel Evo Laptop: A high-performance laptop with Intel Evo (https://www.lenovo.com/in/en/faqs/intel/intel-evo-platform/) certification, featuring the latest processors and ample RAM.
Visual Studio Code Product: Visual Studio Code (Version 1.82)
The Issues:

Performance Issues: My Intel Evo laptop is experiencing performance problems when running Visual Studio Code. This includes slow response times, lagging, and occasional crashes during coding sessions.

Installation and Setup Difficulties: I’ve faced challenges while installing and setting up Visual Studio Code (Version 1.82) on my Intel Evo laptop. Despite following the installation instructions, there might be configuration issues affecting performance.

Extension and Compatibility Problems: There seem to be compatibility issues between the Intel Evo laptop and some extensions or features of Visual Studio Code (Version 1.82). This is impacting the functionality and efficiency of my development work.

Thank you in advance for your help!

What I have tried:

Steps Taken So Far:

- Confirmed that my Intel Evo laptop meets the system requirements for Visual Studio Code (Version 1.82).
- Followed the installation and setup documentation for Visual Studio Code carefully.
- Tried various configurations and system adjustments to improve performance and resolve compatibility issues.
- Despite these efforts, the problems persist. Has anyone experienced similar issues with an Intel Evo laptop and Visual Studio Code (Version 1.82)? Are there specific configurations, optimizations, or troubleshooting methods that have worked for you? Any advice, tips, or resources would be greatly appreciated.

Posted 12-Aug-24 2:40am

Judy Watson

Updated 12-Aug-24 3:24am

Add a Solution

Comments

Dave Kreskowiak 12-Aug-24 18:14pm

You're going to have to give the specs on your machine, CPU, RAM, disk size.

2 solutions

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Pete O'Hanlon · Answer 1 · 2024-08-13T23:30:00

In a version of "have you switched it off and back on again?", I would recommend completely uninstalling VS Code. Once you have done this, restart your PC and reinstall VS Code from here[^].

Once you have installed the new version, don't blindly add extensions. Add an extension at a time - it could well be that you have a rogue extension which is grabbing far more resources than it should. One of the hidden problems with VS Code is, while the editor is excellent, the extensions are largely unregulated so it's very easy to pull in a bad extension. Test the performance of your machine after you install each extension. If you reach a poorly performing point in time, you have identified your rogue extension.

OriginalGriff · Answer 2 · 2024-08-12T18:55:00

Solution 1

I'd suggest you contact MS tech support - if it's a problem with a specific machine or family of machines, they will at least have better data on it than we will - and they may even have a fix.

Posted 12-Aug-24 18:55pm

OriginalGriff