You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jul 11, 2018. It is now read-only.
Opening a JSON "log" file (about 200kB, rough format below) that doesn't contain any formatting / newlines incurs 100% CPU time for about 13 minutes. The code outline then appears correctly and all is well.
Formatting the document, saving and reopening results in no hogging and a delay of just 2 seconds or less before the outline appears.
Whether the hog is from native vscode json or Code Outline I know not. code --status says
CPU% is 100% for extensionHost when hogging occurs
CPU% is 0% for electron_node jsonServerMain.js
Code Outline does not do any document parsing on its own and relies on the SymbolProvider API to be implemented by specific language extensions. I believe the JSON one is built into VS Code itself.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Just an observation, (file under FYI) :
Opening a JSON "log" file (about 200kB, rough format below) that doesn't contain any formatting / newlines incurs 100% CPU time for about 13 minutes. The code outline then appears correctly and all is well.
Formatting the document, saving and reopening results in no hogging and a delay of just 2 seconds or less before the outline appears.
Whether the hog is from native vscode json or Code Outline I know not.
code --status
saysCPU% is 100% for extensionHost when hogging occurs
CPU% is 0% for electron_node jsonServerMain.js
FWIW: JSON format:
The text was updated successfully, but these errors were encountered: