continue Continue crashes extensionHost

Before submitting your bug report

[x] I believe this is a bug. I'll try to join the Continue Discord for questions
[X] I'm not able to find an open issue that reports the same bug
[X] I've seen the troubleshooting guide on the Continue Docs

Relevant environment info

- OS: Arch Linux x64 6.10.7-arch1-1 
- Continue: v0.8.50
- IDE: VSCodium
- Model: Version 1.92.2, Release 24228, Electron: 30.1.2, Chromium: 124.0.6367.243, Node.js: 20.14.0, V8: 12.4.254.20-electron.0
- config.json: 
  
{
  "models": [
    {
      "title": "Local Ollama",
      "provider": "ollama",
      "model": "phi3.5:3.8b-mini-instruct-q5_K_M"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Local Ollama",
    "provider": "ollama",
    "model": "starcoder2:3b-q5_K_M"
  },
  "embeddingsProvider": {
    "provider": "ollama",
    "model": "nomic-embed-text"
  }
}

Description

Continue never starts. It eventually causes a popup to appear in the lower right to restart extensionHost

To reproduce

Eliminate extensions until only Continue is left and causes the error. Try with pre-release version and with different previous release versions. Try now on a new and clean installation. 0. codium --verbose

Install Continue extension.
Activate Continue: click on Continue icon.

ss4 4. Gets output: ... console4.txt

Logs: main.log renderer.log

Log output

DEBUG Comments: URIs of continue on comments to add to storage .
workbench.desktop.main.js:3240 Extension host (LocalProcess pid: 5494) terminated unexpectedly. Code: 0, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:3240
_onExtensionHostCrashed @ workbench.desktop.main.js:3241
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:3240
(anonymous) @ workbench.desktop.main.js:3240
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
_onExtHostProcessExit @ workbench.desktop.main.js:1925
(anonymous) @ workbench.desktop.main.js:1925
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
J @ workbench.desktop.main.js:123
onResponse @ workbench.desktop.main.js:123
onBuffer @ workbench.desktop.main.js:123
(anonymous) @ workbench.desktop.main.js:122
_deliver @ workbench.desktop.main.js:93
_deliverQueue @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
Se @ workbench.desktop.main.js:88
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2
workbench.desktop.main.js:660   ERR Extension host (LocalProcess pid: 5494) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:660  INFO Automatically restarting the extension host.
workbench.desktop.main.js:660  INFO Started local extension host with pid 5584.
webWorkerExtensionHostIframe.html:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
workbench.desktop.main.js:660 DEBUG [Registering Log Channel] File does not exist. Waiting for 1s to retry. file:///home/guest/.config/VSCodium/logs/20240903T143220/window1/exthost/webWorker/workerexthost.log
workbench.desktop.main.js:660 TRACE writeTextAreaState(reason: focusgain)
workbench.desktop.main.js:660 TRACE [text file model] resolve() - enter file:///home/guest/programs/test1-w.-continue.py
workbench.desktop.main.js:660 TRACE [text file model] resolveFromFile() file:///home/guest/programs/test1-w.-continue.py
workbench.desktop.main.js:660 TRACE writeTextAreaState(reason: focusgain)
workbench.desktop.main.js:660  INFO Extension host (LocalProcess pid: 5584) is unresponsive.
workbench.desktop.main.js:3240 Extension host (LocalProcess pid: 5584) terminated unexpectedly. Code: 132, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:3240
_onExtensionHostCrashed @ workbench.desktop.main.js:3241
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:3240
(anonymous) @ workbench.desktop.main.js:3240
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
_onExtHostProcessExit @ workbench.desktop.main.js:1925
(anonymous) @ workbench.desktop.main.js:1925
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
J @ workbench.desktop.main.js:123
onResponse @ workbench.desktop.main.js:123
onBuffer @ workbench.desktop.main.js:123
(anonymous) @ workbench.desktop.main.js:122
_deliver @ workbench.desktop.main.js:93
_deliverQueue @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
Se @ workbench.desktop.main.js:88
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2
workbench.desktop.main.js:660   ERR Extension host (LocalProcess pid: 5584) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:660  INFO Automatically restarting the extension host.
workbench.desktop.main.js:660  INFO Started local extension host with pid 5615.
webWorkerExtensionHostIframe.html:1 An iframe which has both allow-scripts and allow-same-origin for its sandbox attribute can escape its sandboxing.
workbench.desktop.main.js:660 DEBUG Comments: URIs of continue on comments to add to storage .
workbench.desktop.main.js:3240 Extension host (LocalProcess pid: 5615) terminated unexpectedly. Code: 132, Signal: unknown
_onExtensionHostCrashed @ workbench.desktop.main.js:3240
_onExtensionHostCrashed @ workbench.desktop.main.js:3241
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:3240
(anonymous) @ workbench.desktop.main.js:3240
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
_onExtHostProcessExit @ workbench.desktop.main.js:1925
(anonymous) @ workbench.desktop.main.js:1925
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
J @ workbench.desktop.main.js:123
onResponse @ workbench.desktop.main.js:123
onBuffer @ workbench.desktop.main.js:123
(anonymous) @ workbench.desktop.main.js:122
_deliver @ workbench.desktop.main.js:93
_deliverQueue @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
Se @ workbench.desktop.main.js:88
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2
workbench.desktop.main.js:660   ERR Extension host (LocalProcess pid: 5615) terminated unexpectedly. No extensions were activated.
workbench.desktop.main.js:820 Extension host terminated unexpectedly 3 times within the last 5 minutes.
onDidChangeNotification @ workbench.desktop.main.js:820
(anonymous) @ workbench.desktop.main.js:820
_deliver @ workbench.desktop.main.js:93
_deliverQueue @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
addNotification @ workbench.desktop.main.js:820
notify @ workbench.desktop.main.js:1947
prompt @ workbench.desktop.main.js:1947
_onExtensionHostCrashed @ workbench.desktop.main.js:3241
_onExtensionHostCrashOrExit @ workbench.desktop.main.js:3240
(anonymous) @ workbench.desktop.main.js:3240
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
_onExtHostProcessExit @ workbench.desktop.main.js:1925
(anonymous) @ workbench.desktop.main.js:1925
_deliver @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
J @ workbench.desktop.main.js:123
onResponse @ workbench.desktop.main.js:123
onBuffer @ workbench.desktop.main.js:123
(anonymous) @ workbench.desktop.main.js:122
_deliver @ workbench.desktop.main.js:93
_deliverQueue @ workbench.desktop.main.js:93
fire @ workbench.desktop.main.js:93
Se @ workbench.desktop.main.js:88
emit @ VM4 sandbox_bundle:2
onMessage @ VM4 sandbox_bundle:2
workbench.desktop.main.js:93 [Violation] Added non-passive event listener to a scroll-blocking 'touchstart' event. Consider marking event handler as 'passive' to make the page more responsive. See https://www.chromestatus.com/feature/5745543795965952
onWillAddFirstListener @ workbench.desktop.main.js:93
_event @ workbench.desktop.main.js:91
(anonymous) @ workbench.desktop.main.js:88
onWillAddFirstListener @ workbench.desktop.main.js:88
_event @ workbench.desktop.main.js:91
G @ workbench.desktop.main.js:166
createMouseController @ workbench.desktop.main.js:209
re @ workbench.desktop.main.js:209
j @ workbench.desktop.main.js:742
_createInstance @ workbench.desktop.main.js:655
createInstance @ workbench.desktop.main.js:655
createNotificationsList @ workbench.desktop.main.js:823
show @ workbench.desktop.main.js:823
doAddToast @ workbench.desktop.main.js:1918
(anonymous) @ workbench.desktop.main.js:1918
execute @ workbench.desktop.main.js:97
St @ workbench.desktop.main.js:97
(anonymous) @ workbench.desktop.main.js:97
workbench.desktop.main.js:660 DEBUG Comments: URIs of continue on comments to add to storage .
workbench.desktop.main.js:660 TRACE [text file model] resolve() - enter file:///home/guest/programs/test1-w.-continue.py
workbench.desktop.main.js:660 TRACE [text file model] resolveFromFile() file:///home/guest/programs/test1-w.-continue.py















































See above files.

Sep 03 '24 21:09 duane-github

I have the same issue. On linux mint with vs code installed with snap. Issue started with version 8.45.

Sep 04 '24 12:09 constLiakos

I have same issue on ubuntu cinnamon vscode,insiders and VScodium

Sep 06 '24 09:09 terry-cellini

Same here on Fedora.

Sep 06 '24 11:09 jborut

Yep. Same here

- OS: fedora 40 
- Continue: v0.8.51, v0.9.206
- IDE: vscodium 1.92.2 (installed via official repo download.vscodium.com)
- Model: -
- config.json: -

continue.log

Using 0.8.44 fixes issue

May this be connected with fact that I have old CPU that does not supports AVX instructions?

Sep 07 '24 18:09 stone-w4tch3r

The issue come up after install the extension of v0.8.51 and v0.9.207.

The following info is from VS code about box:

Version: 1.93.0
Commit: 4849ca9bdf9666755eb463db297b69e5385090e3
Date: 2024-09-04T13:02:38.431Z
Electron: 30.4.0
ElectronBuildId: 10073054
Chromium: 124.0.6367.243
Node.js: 20.15.1
V8: 12.4.254.20-electron.0
OS: Linux x64 6.8.0-41-generic (Ubuntu 24.04)

Sep 10 '24 08:09 limcheekin

I believe this is caused by https://github.com/lancedb/lance/issues/2195 https://github.com/lancedb/lancedb/issues/1437.

Sep 22 '24 12:09 shockme

any fix here?

Sep 30 '24 15:09 MaxFSP

If your workstation is on a VM like mine (Proxmox), try to change processor type from x86-64-v2 to x86-64-v3 . It requires avx2. That worked for me.

Oct 03 '24 01:10 constLiakos

Same issue on macOS 15.0.1

Oct 08 '24 14:10 roshanbodomlol

Same issue on Linux Lite 7.2

Oct 10 '24 18:10 christoferjh

any fix here?

The fix is to just use Zed (https://zed.dev). It's free, open source, works well and doesn't crash. It has smart integrations with Antropic, OpenAI and Ollama models.

I've been using it and recommend it.

Oct 15 '24 12:10 shockme

My Continue VSCode extension also crashes Extension Host, but only when I use the Remote - SSH or Remote - Tunnels -- It will crash the (local) Extension Host when the network is bad. Even worse, with Remote - SSH that will trigger "cannot reconnect" error. My solution is forcing it to run in the Remote Extension Host by setting.json (see https://code.visualstudio.com/api/advanced-topics/remote-extensions#incorrect-execution-location)

{
    "remote.extensionKind": {
        "Continue.continue": ["workspace"],
    },
}

I found this solution because vscode.dev/tunnel doesn't crash. (actually, only after that I knew the crash is caused by Continue) After that, it took me a few hours to verify the cause and find the method to force it to run in the remote.

Dec 17 '24 19:12 YouJiacheng

Same issue here: v0.9.259 (release & pre-release)

Linux Mint 21.3 Xfce:

Version: 1.96.4
Release: 25026
Commit: 06487dbc453a56dbaa4ce833d9d062396e7f7826
Date: 2025-01-26T12:14:19.860Z
Electron: 32.2.7
ElectronBuildId: undefined
Chromium: 128.0.6613.186
Node.js: 20.18.1
V8: 12.8.374.38-electron.0
OS: Linux x64 5.15.0-131-generic

Feb 01 '25 15:02 mbnoimi

I see this issue on:

Continue: 0.8.68
VS Code: 1.97.0
OS: Ubuntu 24.04.1 LTS  x86_64

I do not see this on ARM architecture:

Continue: 0.8.68
VS Code: 1.97.0
OS: Ubuntu 24.04.1 LTS  aarch64

Both environments are virtualized using VirtualBox. Aside from architecture, the only difference between the two is that the ARM box is Ubuntu server, with the desktop installed via command line. It's host is MacOS Sequoia (M1, Apple Silicon). The x86 guest is hosted on a Windows 11 AMD64 machine. They are both fresh installs with the purpose of testing Continue.

Feb 10 '25 19:02 shermanhuman

well, seems like author does not care to fix it. I am leaving then

Feb 13 '25 11:02 sunshine69

@Patrick-Erichsen introduced some binary updates/handling that may have fixed this

Mar 11 '25 17:03 RomneyDa

This issue hasn't been updated in 90 days and will be closed after an additional 10 days without activity. If it's still important, please leave a comment and share any new information that would help us address the issue.

Aug 06 '25 02:08 github-actions[bot]

This issue was closed because it wasn't updated for 10 days after being marked stale. If it's still important, please reopen + comment and we'll gladly take another look!

Aug 18 '25 02:08 github-actions[bot]