Do these 3 things before closing this tab:
1Clear out junk files and repair common Windows errors2Fix the driver behind crashes, sound loss and screen glitches3Repair Windows errors before they cause bigger problemsiTechGuides is reader-supported. When you buy through links on our site, we may earn an affiliate commission. As an Amazon Associate I earn from qualifying purchases. Learn more
Start with VS Code’s built-in Developer: Show Running Extensions command. It opens the Running Extensions editor, which is the right first place to inspect extension activity. Because the exact columns and metrics can vary by VS Code build, do not assume that it provides a complete per-extension CPU or memory ranking. Pair it with an Empty Profile test, a controlled extension reintroduction, and a repeatable command-line inventory. In remote workspaces, first establish whether the load is on your local machine or the remote workspace host.
What you can—and cannot—measure in VS Code
There are three different questions people often combine when they ask which extension is using the most resources:
- Which extensions are active? The Running Extensions editor is designed for this first inspection.
- Are extensions involved in the slowdown at all? An Empty Profile provides an isolation test by disabling extensions and modified settings.
- Which individual extension is responsible for CPU or memory? The official material available for the Running Extensions editor confirms the command and editor, but does not establish that every current VS Code release displays a complete, sortable per-extension CPU and memory leaderboard.
That distinction matters. A process monitor can show resource use for an extension host, but an extension host may contain work from more than one extension. Conversely, an isolation test can prove that extensions or settings are involved without assigning a number to any single extension. Treat the result as a diagnosis, not as a ranking, unless your installed build visibly supplies per-extension metrics.
The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Use the Running Extensions editor first
Open the editor
- Open the VS Code Command Palette.
- Run Developer: Show Running Extensions.
- Read the Running Extensions editor that opens. Record the extension names, host information, activity indicators, and any CPU, memory, or timing fields that your build actually displays.
The command and editor are documented by Microsoft, but the reference describing them is from the September 2022 (version 1.72) release. Labels, columns, and units in a current installation may differ. If your editor has no CPU or memory column, there is no supported basis for claiming that it ranks extensions by those resources. Do not turn an activation-time or activity indicator into a CPU percentage.
#1 Best Overall
- Powerful Turbo Fan:CAGIWIRU Electric Air Duster have reached speed up to 130000RPM,Can efficient remove dust and debris.With LED light and Three Adjustable Speed to meet with different cleaning tasks.
- With Attached USB C Fasting Charging cable.Charing 3 hours,Enjoy up to 240 minutes of use on the lowest setting, For third speed can use for 25mins.with four charging options to meet with your needs.
- Wide Application: attached 5 different nozzles,making it suitable for a variety of scenes, such as car,pet, pc, keyboards, and other electronic devices. It also serves for office and home clean duster.
- Handy Design & Portable:Cordless air duster electric nozzle is Light weight and small size, design and comfortable to hold and space saving, convenient to carry around. You can put it in your room or inside the car without taking up space.
- Economical &Reusable: Built durable materials with a long-lasting battery,our CAGIWIRU air duster it's a sustainable alternative to disposable air cans.
Capture a useful snapshot
Make the observation reproducible instead of relying on a quick glance:
- Write down the VS Code version and whether the window is local, web-based, or connected to a remote workspace.
- Note what was happening when the problem appeared: opening a large folder, typing, saving, debugging, searching, or running a task.
- Record which extensions appear active and which host they are associated with, if the editor exposes that information.
- Take a screenshot or copy the visible values before changing profiles or disabling anything.
This snapshot is evidence of what your build displayed at one moment. It is not proof that an extension caused the problem, because an active extension can be idle while another component is busy, and a host can service several extensions.
Prove whether extensions are involved with an Empty Profile
Create or select the profile
- Open the VS Code Profiles editor.
- Create or select an Empty Profile.
- Reproduce the same action that triggered high CPU, memory growth, lag, or fan activity.
- Compare the behavior with the original profile.
VS Code describes an Empty Profile as disabling extensions and modified settings. That makes it an isolation control: the test removes two classes of change while leaving the VS Code installation itself available. Keep the original profile intact so you can return to the same workspace and settings after the comparison.
Interpret the comparison
| Observation | What it establishes | What it does not establish |
|---|---|---|
| The issue disappears in the Empty Profile | An extension, a modified setting, or an interaction among them is implicated. | It does not identify one extension or measure its CPU or memory. |
| The issue remains in the Empty Profile | The cause may be VS Code core, the workspace, a task, a language service outside the disabled extensions, or the environment. | It does not prove that every extension is harmless in the original profile. |
| The symptom changes but does not disappear | Extensions or settings may contribute without being the only cause. | It does not provide a reliable percentage or ranking. |
The isolation conclusion is a diagnostic inference from the documented purpose of the Empty Profile. It is intentionally different from a direct resource measurement.
Narrow the suspect list with a controlled reintroduction
If the Empty Profile removes the symptom, reintroduce changes in a controlled sequence. The goal is to reduce the set of possible causes while keeping the reproduction consistent.
Rank #2
- Screen Cleaner is Your Screen’s New Bestfriend! - EVEO is proud to present a screen cleaner that’s perfectly suited for your TV. Meet your new screen cleaner, computer screen cleaner, laptop cleaner, iPad cleaner, Macbook,tv cleaner or any other electronic device. Our screen cleaner spray and wipe along with the included plush microfiber cloth, easily removes dust, fingerprints & other smudges on the screen’s surface. Clean effectively for a streak-free screen
- Gentle on your Screens - Our screen cleaner spray and wipes is compatible to be used even for the most sensitive LCD, LED, CRT, and OLED screens in proper use. Be at ease knowing that this product is compatible with all the major brands: LG, SONY, Samsung, Sharp, iPad, iPhone, Android screens, Kindle, PC monitors - we’ve got you covered! Can be used as LCD screen cleaner, tv cleaner, smart tv screen cleaner, and more
- Premium Super Soft Plush Microfiber Cloth - Included in this efficient screen cleaning kit. This screen cleaner spray and wipe has our signature plush microfiber cloth specially designed to comply with screens and monitors and leave them streak-free. Has been shown to effectively absorbs stubborn stains, zero streaks, and no fiber shedding. Always use this together with our screen cleaner for the best results
- Easy-to-Use Screen Cleaner Kit + microfiber cleaning cloth - The EVEO Screen Cleaning Kit will easily be your new favorite tool when it comes to taking care of the things you love most, quick and easy solution for a streak-free screen. Simply screw on the sprayer gun on the screen cleaner bottle. Spray the cleaning liquid onto the microfiber cloth, then wipe the screen until desired cleanliness & shine is achieved.
- Quality Screen Care Kit Worth Purchasing - Enjoy a convenient Screen Cleaner anytime, anywhere you need it. Your satisfaction is our top priority. We stand behind the quality of our products and that’s why, you shouldn’t be worrying at all. We manufacture the Best Screen Cleaner. and can be used for laptop cleaning kit, laptop screen cleaner, tv screen cleaner for smart tv. MacBook screen cleaner, monitor cleaner or screen cleaner spray for electronic devices with microfiber cleaning cloth
Use groups when you have many extensions
- Return to the original profile and list the installed extensions and versions, using the CLI inventory described below.
- Divide the extensions into two roughly equal groups based on function or installation order.
- Enable or test one group while keeping the other group out of the experiment, then reproduce the same workload.
- Keep the group associated with the symptom and split it again. Repeat until the suspect set is small.
This halving approach is faster than changing every extension at once, but it is still behavioral testing. It identifies a likely contributor under your workload; it does not claim that the extension consumed a particular number of CPU cycles or bytes.
Use one-at-a-time testing for a short list
When only a few extensions remain, test each one separately. Change one variable, restart or reload the window in the same way each time, and perform the same action for the same approximate duration. Record whether the symptom is present, absent, or merely reduced. If two extensions interact, each can appear harmless alone and problematic together, so test the pair after individual checks when the evidence points to an interaction.
Keep the workload constant
- Use the same workspace and folder state.
- Repeat the same edit, search, build, debug, or file-generation operation.
- Allow background indexing or startup activity to settle before comparing observations.
- Do not update, install, or remove extensions in the middle of a comparison.
Without a consistent workload, a change in CPU or memory may reflect different files or tasks rather than the extension you changed.
Build a repeatable extension inventory from the CLI
The VS Code command-line interface can create a record of what is installed, but it is not a resource profiler. Run these commands in a shell where the code command is available:
code --list-extensionsThis lists installed extension identifiers.
code --list-extensions --show-versionsThis lists the identifiers together with their installed versions. Save the output with the date and the VS Code version so you can reproduce the same test after an update.
Rank #3
- 【Large size】：Measuring 800 x 300 mm/ 31. 5×12 inches, which is wider and taller than others. Large mouse pad can perfectly fit your keyboard and mouse of any size, and there is also ample space for peripherals such as phones, tablets, etc.
- 【LED backlight mouse pad】：Blade Hawks RGB mouse pad provides 7 static modes and 7 dynamic modes will give you the options you are looking for. Power-off memory function remembers the last lighting mode you selected. The super glow fiber Chroma will give you a colorful gaming setup that you want.
- 【Anti-slip rubber base】：Made from Natural rubber, this gaming mousepad will firmly grip your desktop, allowing you to enjoy the ultimate precision in the games you are most passionate about. It also comes with a texture that enhances this ability even further.
- 【Smooth and waterproof surface】: Micro-textured cloth surface, for extremely precise mouse control and a smooth movement. When liquid splashes on the gaming mouse pad, it forms water droplets and slides down. Will not delay your work or gameplay.
- 【Plug and play】: This mouse and keyboard pad is powered by USB, plug and play, no driver required. One button control light modes. Press one time to change the lighting mode, press twice to change the brightness, press and hold about 3 seconds turn ON/OFF.
code --disable-extensionsThis starts VS Code with all installed extensions disabled. It is useful for a command-line baseline or a quick confirmation, but it does not tell you which extension would have used the most CPU or memory. It also differs from selectively disabling one extension: every extension is removed from that run.
Recommended Free Tools
These options answer inventory and isolation questions. They do not emit per-extension CPU percentages, memory totals, a ranking, or a historical trace.
Identify which machine is doing the work
VS Code can run extensions in local, web, or remote extension hosts. Placement depends on the extension’s capabilities, your configuration and placement preference, and where the extension is installed. In a remote development setup, the process consuming resources may be on the workspace host rather than on the computer displaying the VS Code window.
Local workspace
For a local folder, inspect the Running Extensions editor and your operating system’s process view together. A process view can tell you whether an extension host is consuming CPU or memory, while the VS Code editor helps you understand which extensions are active in that host. Treat the process number as host-level evidence unless your build explicitly attributes usage to an individual extension.
Remote workspace
For an SSH, container, or other remote workspace, check both sides:
Rank #4
- 【Softer and More Comfortable】Vaydeer wrist rest has unique diamond pattern, which is the combination of softness and aesthetics. The materials of wrist rest are improved into higher quality memory foam and covered with silky smooth lycra. The computer wrist rest makes you as comfortable and cushiony as like rest your wrists on clouds.
- 【Ergonomic Wrist Saver】The wrist rests for keyboard and mouse comes with a 17.32×3.15×0.83 inch keyboard wrist pad and a 5.94×3.15×0.83 inch mouse wrist support. Based on ergonomic design, the unique concave shape is the perfect fit for your wrist joints. The wrist rest pad fits most computer keyboards and laptops, improve hand and wrist posture, release your wrist and arm stress.
- 【Non-Slip Rubber Bottom】Featuring an anti-skid silicone base on the bottom, this wrist keyboard support stays firmly in place on your desk, preventing the padding from sliding around, ensuring stable and consistent wrist support during extended computer sessions.
- 【Better Experience & Pain Relief】Our keyboard arm rest is beneficial to alleviate the soreness caused by direct contact and friction between your arm and a hard desk surface, reducing the risk of wrist fatigue or carpal tunnel. The soft texture of memory foam can evenly distribute the pressure around your wrists and provide good support with just enough give.
- 【Helpful in Multiple Scenarios】Whether you're working, studying, writing, typing, gaming, this keyboard and mouse rest combo is an essential accessory to add comfort and support to your hands and wrists. It’s also a great gift for men, women, family, friend, coworker, gamer, teacher, etc.
- On the local UI machine, look for resource use associated with the VS Code window or local extension host.
- On the remote workspace host, inspect the processes there, because remotely placed extensions execute there.
- Use the Running Extensions editor to see the placement information your build exposes, and note where each extension is installed.
Reading only the local task manager can lead to the wrong conclusion: a quiet local machine does not rule out a busy remote extension host.
Web sessions
In a browser-based VS Code session, distinguish browser-tab activity from work performed by a remote workspace host. The same extension may not execute in the same place in every environment. Record the session type before comparing measurements from different machines.
When the editor does not show a per-extension ranking
That outcome is itself useful information. Use this decision path:
- Does the Running Extensions editor expose CPU or memory values? If yes, verify the units, time window, and whether sorting is available before calling it a ranking.
- If not, does an Empty Profile remove the symptom? If no, investigate workspace tasks, VS Code core, and the environment rather than blaming an extension.
- If yes, can controlled groups reproduce the symptom? Narrow the suspect set by changing one group at a time.
- Can the suspected extension be reproduced alone? Test it in a clean profile or a minimal workspace and record the workload that triggers the issue.
- Is the host local or remote? Attribute process observations to the correct machine before taking action.
This method produces a defensible “likely contributor” finding even when no built-in leaderboard exists. It deliberately avoids inventing precision that the installed build does not provide.
Common interpretation errors
- Assuming active means expensive: An extension can be running but idle.
- Assuming one host equals one extension: A host process can service multiple extensions.
- Reading a single spike as a leak: Startup, indexing, or a one-time task can be brief and expected; compare repeated runs.
- Comparing different workspaces: File count, language mix, generated files, and tasks can change the workload.
- Ignoring settings: An Empty Profile disables modified settings as well as extensions, so disappearance of a symptom does not isolate the extension by itself.
- Mixing local and remote observations: A process on the workspace host will not appear in the local machine’s process list.
- Treating CLI output as telemetry:
--list-extensionsand--show-versionsidentify software; they do not measure it. - Assuming documentation from an older release describes today’s columns: Confirm the fields visible in your own Running Extensions editor.
A practical incident worksheet
For a problem you need to revisit or report, keep one record containing:
Best Value
- 【No Drill Mounted】Cable management tray can be assembled in as little as 3 minutes or less-simply. Side clips easily clampe the edge of desk, pass through the holes on the sides, and secure excess cables with baskets. Desk cable management supports inward or outward installation to meet your needs in different scenarios, and provides you with great convenience when collecting and organizing wires.
- 【Rubber Pad Protects Desk】Wire organizer under desk built-in soft rubber pads on the clamp protect your desk from scratches, so you will not damage your furniture or office.
- 【Sturdy and Beautiful】Cord management under desk is made of high-quality carbon steel and holds about 15 lbs. The wire basket has 2 holes on each side of the tray to enable your cables to pass freely. Cable baskets are suitable for desk thickness use from 0.4" to 2.4".
- 【Space Saving & Keep Organized】Desk cable management tray holds all your power cords, outlet strips, USB hubs and computer transformers hidden from your feet, and the data cables will not enter the vacuum cleaner to keep your desk clean and tidy. Desk wire organizer is also suitable for use in the kitchen and outdoors.
- 【Reduce Safety Risks】Cable tray under desk keeps all plugs away from your kids, no more worry about tripping. Using 2 holes wire tray saves extra space, helps you easily cabling and wire protection. The mesh design is not easy to accumulate dust, but avoids safety accidents caused by messy wires.
| Field | Record |
|---|---|
| Environment | VS Code version, operating system, local/web/remote session, and workspace type. |
| Trigger | The exact action that produces the slowdown or resource increase. |
| Running Extensions view | Visible extension names, host information, and any metrics or units shown by your build. |
| Baseline | What happened with an Empty Profile and, if used, with code --disable-extensions. |
| Inventory | Output from code --list-extensions --show-versions, saved with a date. |
| Controlled tests | Which group or individual extension was enabled for each reproduction and what changed. |
| Host location | Whether the observed process was on the UI machine or the workspace host. |
This record separates observations from conclusions and makes it possible to repeat the test after an extension or VS Code update.
What a reliable conclusion looks like
A strong conclusion states the evidence and its limits: for example, “The symptom reproduced in the normal profile, disappeared in an Empty Profile, and returned when group B was reintroduced; the remaining suspects were tested individually on the remote workspace host.” That is more accurate than saying “Extension X used 73% CPU” when no per-extension measurement was displayed.
If your build does show explicit per-extension CPU and memory fields, record the labels and units exactly as shown, note the observation window, and repeat the same workload before comparing values. If it does not, report a likely contributor based on controlled isolation and identify the host where the aggregate process load occurred.
Current-version caveat
The command Developer: Show Running Extensions and the Running Extensions editor are established entry points. The available documentation does not establish a universal set of current columns, units, or sorting behavior for every VS Code release. Verify those details in the build you are troubleshooting rather than relying on screenshots or instructions written for an older version.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
