vscodium autocomplete issues

[NTchrist]

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: Ubuntu 24.04 || Windows 11
- Continue version: (any, 1.1.24 & 1.1.29 at time of report)
- IDE version: vscodium (latest, 1.99.32704 at time of report)
- Model: qwen2.5-coder:7b
- config:
  
name: Local Assistant
version: 1.0.0
schema: v1
models:
  - name: deepcoder:14b-preview-q4_K_M
    provider: ollama
    apiBase: http://192.168.248.97:11434
    model: deepcoder:14b-preview-q4_K_M
    roles:
      - autocomplete
      - chat
  - name: qwen2.5-coder:7b
    provider: ollama
    apiBase: http://192.168.248.97:11434
    model: qwen2.5-coder:7b
    roles:
      - autocomplete
      - chat
  - name: qwen2.5-coder:1.5b
    provider: ollama
    apiBase: http://192.168.248.97:11434
    model: qwen2.5-coder:1.5b
    roles:
      - autocomplete
      - chat
  - name: nomic-embed-text
    provider: ollama
    apiBase: http://192.168.248.97:11434
    model: nomic-embed-text
    roles:
      - embed
context:
  - provider: code
  - provider: docs
  - provider: diff
  - provider: terminal
  - provider: problems
  - provider: folder
  - provider: codebase
rules:
  - use 2 spaces instead of tabs

Description

While autocomplete is enabled, after a seemingly random amount of time (as short as 15 minutes; as long as a few days) the plugin and all of its features will go unresponsive. When this happens, the hallmark other symptoms are that:

• One cpu thread will spike up to 100% and will stay there indefinitely until vscodium is closed.
• You will be unable to copy from the editor via ctrl+c.
• The editor will be generally slow to use, saving will take 3-5 seconds, etc.

Indexing enabled/disabled doesn't appear to make a difference. It may be the same issue as https://github.com/continuedev/continue/issues/4756 and those in the thread just didn't run vscodium long enough to experience it again, but I'm definitely unable to fix this issue by disabling indexing in the UI, or by editing /CodebaseIndexer.ts as suggested in that thread. Additionally, I still exhibit the same symptoms with a nightly build of continue that doesn't console error with "config is undefined" as nightly builds did a few weeks ago under vscodium. I believe that to be a red herring.

I first ran into this issue about a year ago with a different ollama server and different computer. I was using the latest vscodium with both the latest stable/nightly builds of continue at the time. I uninstalled it after a few days and did not try again until April 21, where I noticed the same issues persisted on two different computers (one win11, one ubuntu) both with vscodium.

I have observed that I can generally leave it idle for an indefinite amount of time without it breaking. I generally observe a break condition right after an autocomplete that I ignore.

I chatted with some devs in the discord, and provided some logging that is no longer present in the current nightly build (1.1.29) that was erroring in the previous version (1.1.24)

It appears to be unrelated.

The only relevant logging that vscodium registers is after it breaks.

To reproduce

1. Install fresh vscodium
2. connect it to an ollama server via the config
3. enable autocomplete
4. use it until it breaks

Log output

workbench.desktop.main.js:35  INFO Extension host (LocalProcess pid: 1193793) is unresponsive.
workbench.desktop.main.js:3256 Extension Host
workbench.desktop.main.js:3256 Debugger attached.
workbench.desktop.main.js:35  INFO UNRESPONSIVE extension host: starting to profile NOW