Issue Type: Bug
"Extension Host is unresponsive" dialog occasionally pops up.

I don't know how to reproduce it, it just occasionally pops up. I tried disabling all my extensions, restart VS Code but it popping out.
Sometimes this dialog will show up:

VS Code version: Code - Insiders 1.28.0-insider (a542a0afb5ff12a878dcf4b6a914f10d1318cb2e, 2018-09-14T05:12:35.372Z)
OS version: Darwin x64 17.7.0
System Info
|Item|Value|
|---|---|
|CPUs|Intel(R) Core(TM) i5-5250U CPU @ 1.60GHz (4 x 1600)|
|GPU Status|2d_canvas: enabled
checker_imaging: disabled_off
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
webgl: enabled
webgl2: enabled|
|Load (avg)|13, 11, 8|
|Memory (System)|8.00GB (0.02GB free)|
|Process Argv|/Applications/Visual Studio Code - Insiders.app/Contents/MacOS/Electron --inspect-extensions=4355|
|Screen Reader|no|
|VM|0%|
Extensions (14)
Extension|Author (truncated)|Version
---|---|---
Bookmarks|ale|9.0.3
disableligatures|Coe|0.0.8
gitlens|eam|8.5.6
vsc-material-theme|Equ|2.4.2
php-debug|fel|1.12.5
php-intellisense|fel|2.3.5
vscode-pull-request-github|Git|0.1.5
beautify|Hoo|1.4.3
path-autocomplete|ion|1.12.0
vscode-insertdatestring|jsy|2.2.3
vscode-phpfmt|kok|1.0.30
es6-css-minify|olb|2.0.3
selectline-statusbar|tom|0.0.2
html-css-class-completion|Zig|1.17.1
(4 theme extensions excluded)
I think this has to do with something involving "Git" extensions like Git Lens or Git History.
I am facing the same issue as well. Do you know the root cause? Any solution please?
Same
Same
same, is there a way to turn of this notification ... it jumps every 2-3 seconds
it started showing after latest update and since then the editor is unusable
got this also only in my windows laptop, linux works fine!
Its happening on my Macbook too. I am using Sublime text till this get fixed.
Same problem
Ubuntu 16.10 with Visual Studio's last update (1.28.0)
Same problem, windows 10.
Same thing on macOS Mojave
1.28.1 seems to have solved the problem, right ? I don't have the error popping anymore
Most helpful comment
Same