Skip to content
OrionHub Developer tooling and cloud development
Section
dev-tools
Kind
Editorial
Reading time
2 min
Updated
8 September 2026

Conquer Code Editor Lag: A Homegrown Diagnostic Guide

If your trusty code editor has slowed to a crawl, take a methodical approach. Most editors have built-in tools to isolate the culprit: reproduce the slowdown, bisect the extensions, then read the configuration profile. In current versions of Microsoft’s Visual Studio Code, this means starting from the “Help” menu, and working through steps published on 16 February 2021:

  1. Run “Help: Start Extension Bisect”. [This launches a diagnostic tool.]
  2. Follow the prompts by answering “Good now” or “This is bad” until the problematic add-on is identified. [The tool uses binary search, so this narrows the range each step by half.]
  3. For a deeper punch, open up the running-extensions view, and under “Developer: Show Running Extensions”, use the run control in its title bar to profile unreliable extensions. [There are numeric performance profiles attached on that page that require no external analytics tool.]

Microsoft's documentation as of September 2025 covers this workflow, but newer versions will still document this workflow both on their GitHub and on a separate DeepWiki that maintains snapshots of the official documentation.

This approach beats a brute-force reinstall, and is superior to ignoring the slowdown. The Visual Studio Code team [breaks down the slow startup into "bisect steps", so it is not an unexplained delay in one place.

If you document the problem in detail, your careful work can even help other developers who report the issue on GitHub, attached to the relevant performance profiles you generated

Writing up a reproducible case that tells developers which symptoms relate to which extension misses out if you knock everything off the table. If your report shows an unusual slow response to keystrokes in the context of certain lines of code, and is attached to a CPU profile instead of just saying "my editor is slow", you will have helped isolate a problem for the Visual Studio Code team in issues documented since May 2025

Microsoft documents this workflow in the Visual Studio Code support site in the VSC wiki formatted on the 5th of September 2025, and in the by May 2025. To justify that effort, you need to have taken the specific notes and bisected results the Dev team is looking for, per the Visual Studio Code bisect documentation, explaining that Code's default EDI document profiles have specifically developed options tuned to that workflow of bisecting and profiling.

You cannot reasonably attribute the specific cause so much

  • you are not randomly testing or identifying which traits in extensions lead to broad-stroke issue reports that will be responded to fast—only a trusted source could say what specific causes will accelerate that ticket-response handling.

Your aim is to use the tools they provided to clarify the sort of ticket that will have the team’s full attention: one with objective metrics of the sluggishness, as measured from the editor profile menu during extension bisect, not vague annoyance. If the official docs don’t claim specific suspected extension types — like instant-language servers or cost of file-watchers or keystroke formatters — deducing those impactful generalizations is a step further than documenting the extension bisect you used. Let’s not overclaim what Visual Studio Code’s official documentation has explicitly shown they can do.