Markdown All in One Documentation

Reporting a performance issue

Before proceeding

It can be frustrating to find the editor unresponsive. But most of the time, it is not our product but the complex interaction between VS Code extensionsopen in new window that causes the problem.

Therefore, please do a quick check as described below.

TIP

To run a command, open Command Paletteopen in new window (Ctrl / ⌘ + Shift + P).

As of VS Code version 1.52open in new window, run VS Code command "Start Extension Bisect". It then guides you.

Traditional

  1. Open a workspace, where you can reproduce the issue.

  2. Run VS Code command "Duplicate Workspace in New Window" to temporarily create a copy for test.

    DANGER

    This step is strongly recommended. Otherwise, you might have a hard time in resetting environment.

    VS Code still does not provide a friendly way to manage workspace storage. (microsoft/vscode#32461open in new window) Thus, if it's polluted accidentally, you will have to reset the workspace state by low-level methods:

    1. Go to the workspaceStorage folder, which is next to the user settings fileopen in new window.

    2. Find the subfolder that holds your workspace storage.

    3. Delete corresponding state.vscdb files. Or, if you have a SQLite 3 database editor, you can try to modify them.

  3. Run VS Code command "Disable All Installed Extensions for this Workspace".

  4. Run VS Code command "Reload Window".

  5. See if you can reproduce the issue.

  6. Only enable this extension (yzhang.markdown-all-in-one).

  7. See if you can reproduce the issue.

How to report

If you believe you have experienced a performance regression caused by our product, please report it to us as described below.

First, download the latest dev buildopen in new window, extract the debug.vsix, and install it via VS Code command "Install from VSIX".

Then, create a Bug reportopen in new window. Please read Collecting diagnostic data, and include the requested information listed below (as much as you can provide) to help us better understand the nature of the possible issue:

  • (Required) A CPU profile. (.cpuprofile.txt)
  • A Markdown file to reproduce. (.md.txt)
  • The commit SHA of the dev build.
  • Basic environment information.
  • Extended environment information.

Please understand that if we cannot gather enough information to diagnose in 30 days, your report will be ignored and closed at any time.