outline view is always slow and loading, code cannot be folded.

[qdechochen]

Issue Type: Bug

• VSCode Version: 1.25.1
• OS Version: Mac OS 10.13.5

Steps to Reproduce:

Since my last post was closed, I have to post again.
I need to say first: I have disabled all extensions, and I've never installed the local history extension.

1. open a js file.
2. change something, and save
3. outline is loading..... and code cannot be folded until outline view is ready (nothing happends when click -/+. Sometimes, the fold symbols( -, +) disappear, and when outline view is ready, they will be back.

it's annoying especially when i want to see some code which is folded, and i can't unfold it.

VS Code version: Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:33:29.235Z)
OS version: Darwin x64 17.6.0

System Info

Item	Value
CPUs	Intel(R) Core(TM) i5-7267U CPU @ 3.10GHz (4 x 3100)
GPU Status	2d_canvas: enabled flash_3d: enabled flash_stage3d: enabled flash_stage3d_baseline: enabled gpu_compositing: enabled multiple_raster_threads: enabled_on native_gpu_memory_buffers: enabled rasterization: enabled video_decode: enabled video_encode: enabled vpx_decode: enabled webgl: enabled webgl2: enabled
Load (avg)	3, 4, 4
Memory (System)	16.00GB (1.65GB free)
Process Argv	/Applications/Visual Studio Code.app/Contents/MacOS/Electron --disable-extensions
Screen Reader	no
VM	0%

Extensions disabled

[vscodebot]

(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:

• outline view is always slow and loading, code cannot be folded. (#54449)
• Add outline settings title "Outline" (#53285)

[jrieken]

Please follow this guide to track down what's slow https://github.com/Microsoft/vscode/wiki/Performance-Issues#profile-the-running-extensions

[qdechochen]

@jrieken Here's the tracking file. thank you.

As what i mentioned before, i disabled all extensions, while problem is still there.

PS: i got my macbook hot all the time. mmmmm, maybe i can bake something on it 😂

CPU-20180718T082407.627Z.cpuprofile.txt

for convenience:

[jrieken]

Looks pretty idle doesn't seems to be in the extension host. Please check via code --status as described here: https://github.com/Microsoft/vscode/wiki/Performance-Issues#collect-information-about-the-running-vs-code

[qdechochen]

@jrieken Here's the screenshot, thank you.

[jrieken]

Hm, if at all it's the TypeScript extension (or its server) but 62% CPU doesn't sound outrageous...

[qdechochen]

60-70% CPU can lasts for serveral minutes, and the outline is not shown correctly, i can't fold or unfold code. When CPU take up rate comes to 0, everything becomes normal.

PS: there are no ts files in the folder, only js files.

[qdechochen]

Hello? Anything else that I can do here? @mjbvz

[mjbvz]

Does this reproduce in the latest VS Code insiders build with all extensions disabled?

[qdechochen]

@mjbvz Latest VS Code insiders build has the same problem on my mac.

[richsilv]

I believe I have a similar problem. Profiling the extensions reveals nothing - they all seem to be behaving themselves, but code outline and autocompletion are taking minutes to refresh, the latter displaying Loading... for ages if I Ctrl-Space. This is a new issue which I've only just started to experience - previously, everything ran fine in the same workspace.

Here's my --status output in case it's helpful:

--- platform/documentation ‹documentation-site-emotion* M?› » code --status
Gtk-Message: 11:39:28.795: Failed to load module "overlay-scrollbar"
Gtk-Message: 11:39:28.808: Failed to load module "canberra-gtk-module"

Version:          Code 1.25.1 (1dfc5e557209371715f655691b1235b6b26a06be, 2018-07-11T15:40:20.190Z)
OS Version:       Linux x64 4.15.0-29-generic
CPUs:             Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz (4 x 2872)
Memory (System):  15.40GB (6.90GB free)
Load (avg):       2, 2, 1
VM:               0%
Screen Reader:    no
Process Argv:     /usr/share/code/code . --inspect-extensions=9333
GPU Status:       2d_canvas:                    enabled
                  flash_3d:                     enabled
                  flash_stage3d:                enabled
                  flash_stage3d_baseline:       enabled
                  gpu_compositing:              enabled
                  multiple_raster_threads:      enabled_on
                  native_gpu_memory_buffers:    disabled_software
                  rasterization:                disabled_software
                  video_decode:                 unavailable_software
                  video_encode:                 enabled
                  vpx_decode:                   unavailable_software
                  webgl:                        enabled
                  webgl2:                       enabled
CPU %	Mem MB	   PID	Process
    2	   110	  4832	code main
    0	    16	  4843	   zygote
    6	   284	  4920	     window (● button.tsx - documentation - Visual Studio Code)
    0	    47	  4961	       watcherService
    0	   205	  4964	       extensionHost
    0	   110	  5063	         electron_node tslintServer.js 
    0	    47	  5113	         electron_node jsonServerMain.js 
    0	    47	  5049	       searchService
    0	   110	  5015	     shared-process
    3	    63	  4909	   gpu-process
Workspace Stats:
|  Window (● button.tsx - documentation - Visual Studio Code)
|    Folder (documentation): 121 files
|      File types: json(56) js(37) md(6) tsx(6) png(3) ts(2) svg(2) snap(1)
|                  gitignore(1) log(1)
|      Conf files: package.json(1) tsconfig.json(1) tslint.json(1)
|                  settings.json(1)

[mjbvz]

@richsilv Please open a separate issue

@qdechochen Can you please try collecting the TS Server log:

1. Set "typescript.tsserver.log": "verbose",
2. Restart VS Code and reproduce the problem
3. In VS Code, run the TypeScript: Open TS Server log command
4. This should open a folder with a tsserver.log file in it

Look through that log file for errors or stack traces. If you can share the log, I can also take a look to see if anything stands out

⚠️Warning: The TypeScript log may include information from your workspace, including file paths and source code. If you have any concerns about posting this publicly on Github, just let me know and we can arrange something else. On our side, we only use these logs to investigate issues like this