Autocomplete Freezing and Locking Up the IDE

[Patrick-Erichsen]

Below is an AI generated summary of the following related issues:

• https://github.com/continuedev/continue/issues/5213
• https://github.com/continuedev/continue/issues/4845
• https://github.com/continuedev/continue/issues/4376
• https://github.com/continuedev/continue/issues/3709
• https://discord.com/channels/1108621136150929458/1367755318670528575
• https://github.com/continuedev/continue/issues/5774
• https://github.com/continuedev/continue/issues/4130

Summary of JetBrains IDE Freezing

Root Cause:

The primary root cause appears to be related to the autocomplete functionality in the JetBrains plugin, leading to the IDE freezing or becoming unresponsive. This is often (but not always) accompanied by high CPU usage from the continue-binary process. A secondary, possibly related, issue involves errors during the indexing/embedding process, specifically "Table already exists" errors with LanceDB.

Affected Versions & IDEs:

• Continue Plugin Versions: Issues have been reported across various versions, including 0.0.75, 0.0.83, 0.0.85, 0.0.88, 1.0.2, 1.0.8, 1.0.17, and 1.0.18 (0.0.75 appears to be the last version that definitely does not experience the issue)
• JetBrains IDEs: IntelliJ IDEA, WebStorm, CLion, Rider, RustRover.
• IDE Versions: Primarily 2024.x versions (e.g., 2024.3, 2025.1 EAP).
• Operating Systems: Windows (10, 11), macOS, Linux.

Note: IDEA 2025.1 in particular has freezing issues across a number of plugins. See this issue for details.

Symptoms & User Reports:

1. IDE Freezing/Hanging:

   • The most common complaint is the IDE becoming completely unresponsive, often when typing or when autocomplete is triggered.
   • Users often need to kill the IDE process via Task Manager or similar.
   • Freezing can occur within minutes of starting the IDE or after a period of normal use.
   • Some users report freezing even with the tab autocomplete feature disabled in settings.

2. High CPU Usage:

   • The continue-binary process is frequently reported to consume high CPU (50-300%, sometimes pinning a core at 100%).
   • However, some users experience freezes without high CPU usage from continue-binary.

3. Autocomplete Issues:

   • Autocomplete suggestions stop appearing.
   • IDE freezes when IntelliJ's native suggestions try to pop up.
   • Stack traces often point to AutocompleteService and related classes.
   • Disabling tab autocomplete in config.json or via IDE settings is a common workaround, but doesn't always resolve the freezing for everyone.
   • Removing keyboard shortcuts related to "Autocomplete" in JetBrains keymap settings has helped some users.

4. Indexing/Embedding Errors:

   • Error messages like: Error: Table 'fileUserssrccatalog-aimainvectordbbRAnomic-embed-text500' already exists.
   • Re-indexing shows files being re-indexed but doesn't resolve the underlying problem or improve context quality.
   • Context only injects a single, incorrect file.
   • Skipping files (e.g., .drawio) during indexing due to "did not chunk properly".

5. Interaction with Other Plugins/Features:

   • One user noted a potential conflict or interaction with com.intellij.codeWithMe (Code With Me feature). Disabling it delayed but didn't always prevent crashes.
   • Disabling other plugins (like "Grazie" and "Grazie Professional" or "JetBrains AI Assistant") was suggested as a potential fix for some users in one thread, but its general applicability is unclear.

Steps Users Have Taken (Workarounds & Troubleshooting):

• Disabling Autocomplete:
  • Commenting out or removing the tabAutocompleteModel section in config.json.
  • Unchecking "Enable Tab Autocomplete" in the Continue plugin settings within the IDE.
  • Removing Continue-related autocomplete keyboard shortcuts in IDE settings.
• Downgrading Plugin Version:
  • Some users found older versions like 0.0.75 to be more stable, although potentially lacking features like copy-paste from the plugin window.
• Clearing Index / Resetting Continue:
  • Deleting the ~/.continue (or ~/.continue_dev) folder to force a fresh start and re-indexing. This was suggested by a maintainer for indexing-specific errors.
• Restarting IDE / Reinstalling Plugin:
  • Temporary relief for some, but the issue often returns.
• Killing continue-binary Process:
  • Some users found that manually killing the high-CPU continue-binary process temporarily resolved the freeze, allowing the IDE to function again. For others, this did not help.
• Checking Ollama/Model Configuration:
  • Ensuring that models specified in config.json (especially for autocomplete) are actually installed and accessible if using local models via Ollama.

Maintainer Actions & Responses:

• PR #3726 was intended to fix a blocking issue on the EDT in JetBrains related to autocomplete latency improvements. Released in 0.0.86.
• PR #5600 was also mentioned as a potential fix for freezing issues. However, users reported freezing persisted even with 1.0.17 and 1.0.18.

Recommendations for Users (Temporary Resolutions):

1. Disable Autocomplete (Most Effective Workaround):
   • Go to your IDE's Continue plugin settings and uncheck "Enable Tab Autocomplete".
2. Clear Index Folder (for "Table already exists" or context issues):
   • Close your IDE.
   • Delete the ~/.continue/index folder (or ~/.continue_dev/index).
   • Restart your IDE. The index will be rebuilt.
3. Try an Older Version (e.g., 0.0.75):
   • If stability is paramount and current versions are unusable, consider manually installing an older version from the JetBrains marketplace version history. Be aware that you might lose recent features or bug fixes.
4. Monitor continue-binary Process:
   • If your IDE freezes, check your system's task manager for a continue-binary process with high CPU usage. If found, try terminating it. This may unfreeze the IDE, but the issue will likely recur.
5. Ensure Local Model Availability: If using Ollama or another local provider for autocomplete, double-check that the model specified in config.json is downloaded and running correctly.
6. Report Issues with Details: If you continue to experience problems, report them on the GitHub issues page, providing:
   • Your Continue plugin version.
   • Your JetBrains IDE and version.
   • Your Operating System.
   • Your config.json (please redact any sensitive keys).
   • Relevant logs from ~/.continue/continue.log.
   • Steps to reproduce the freeze if possible.
   • Any IDE thread dumps if the IDE generates them upon freezing.

[a12233]

I am having this issue when I lock my screen with IntelliJ open and unlock my screen after a period of time. IntelliJ is unresponsive and needs to be Force Quit.

• OS: MacOs 15.5
• Continue version: 1.0.16
• IDE version: IntelliJ IDEA 2024.2.5 (Ultimate Edition)

If I minimize IntelliJ and do the same lock screen, wait, return, maximize application I do not see the "freezing" behavior

[RomneyDa]

@a12233 this may have been fixed by #5600 , could you try 1.0.17?

[glm1024]

Starting from version 0.77, JetBrains IDEs consistently freeze after triggering autocomplete several times. However, when autocomplete is disabled, the crash no longer occurs. This issue does not occur in VS code, where autocomplete works as expected.

[glm1024]

To reproduce the issue, keep triggering autocomplete continuously around 20 to 30 time. JetBrains IDEs will freeze after several invocations.

[danielzgtg]

Has anyone run jstack on the frozen process?

[ruchernchong]

@a12233 this may have been fixed by #5600 , could you try 1.0.17?

Problem still persisted for me even in 1.0.18 EAP.

[auderson]

@a12233 this may have been fixed by #5600 , could you try 1.0.17?

Problem still persisted for me even in 1.0.18 EAP.

Same in 1.0.18

[Hakenadu]

IntelliJ IDEA 2025.1.1 (Ultimate Edition) Build #IU-251.25410.109, built on May 7, 2025 Runtime version: 21.0.6+9-b895.109 amd64 (JCEF 122.1.9) VM: OpenJDK 64-Bit Server VM by JetBrains s.r.o.

Continue Plugin Version 1.0.18

Since upgrading the jetbrains version the freezing problem also occurs frequently with no autocomplete model configured just by using the integrated Chat Widget

edit: pardon - this seems to be a different issue. just the continue chat ui freezes and becomes unresponsive until the ide is restarted. I'll try to find a matching Issue for that.

[Patrick-Erichsen]

@Hakenadu there are a few other users that have reported this too but I don't recall the issue number, if you find it definitely drop it here!

[NTchrist]

other potential reports of the same issue (from issues that mirror my own symptoms)

https://github.com/continuedev/continue/issues/5843 https://github.com/continuedev/continue/issues/4756

[Patrick-Erichsen]

Thanks for the related issues @NTchrist . I'm relatively certain https://github.com/continuedev/continue/issues/5843 is unrelated but it's also on radar.

[NTchrist]

@Patrick-Erichsen

Seems odd that you'd have two different issues related to autocomplete logic that block copying from the ide, but I've not taken a deep-dive into this codebase so I'll defer to your expertise on this one.

[Patrick-Erichsen]

That issue is specifically code related to the VS Code extension. I think the root issue here likely has to do with some threading logic in the JetBrains extensions.

[Hakenadu]

Is this problem maybe related to and fixed by switching to the intellij built-in api for inline completions?

#2061

[nethopper]

FYI I think I encountered a related problem in macOS VSCode. Autocomplete would hang, then kill the extension host every time. Turns out it was caused by having a git diff of ~100M characters (don't judge me!). After cleaning up the diff, autocomplete works as expected. Thank you to Owen in Discord for tracking this down.

Error dump for googleability:

Extension host (LocalProcess pid: 28723) is unresponsive.
[Extension Host] Error generating autocompletion:  RangeError: Invalid array length
    at Array.push (<anonymous>)
    at LlamaTokenizer.mapCharactersToTokenIds (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:129419:22)
    at LlamaTokenizer.encode (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:129446:31)
    at LlamaEncoding.encode (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:130358:39)
    at countTokens (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:130134:21)
    at getSnippets (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:137845:29)
    at renderPrompt (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:137977:20)
    at CompletionProvider.provideInlineCompletionItems (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:139765:74)
    at async ContinueCompletionProvider.provideInlineCompletionItems (/Users/bartek/.vscode/extensions/continue.continue-1.0.10-darwin-arm64/out/extension.js:641868:27)
    at async _n.provideInlineCompletions (

[RomneyDa]

@nethopper thanks for the report. It seems like this is less common in VS Code but still happens. I opened a PR to remove git diff from autocomplete retrieval here https://github.com/continuedev/continue/pull/5882

[Symfomany]

Have you last version of IDE/Plugin Continue ?

[RomneyDa]

@Symfomany have you tried it? Is it fixed for you on 1.0.21+?

[NTchrist]

were the fixes for this ported over to the vscode/vscodium plugins or was that fix targeted specifically for jetbrains?

[nc-jkleinowitz]

I had quite a lot of freezes with IntelliJ IDEA 2025.1.1.1, Build #IU-251.25410.129 + Continue Plugin 1.0.21. Here's a relevant output of running eu-stack -idv -p %CONTINUE_PROCESS_ID% during a hang, maybe that helps?

Most notable is 59034, I'm not quite sure whats going on here. This process was using 100% CPU during the freeze. There were a lot of entries similar to 59036 and 59451, I have removed those.

PID 59034 - process
TID 59034:
#0  0x000011a9239059d2    
#1  0x000011a923923ee1 - 1
#2  0x000011a923906b95 - 1
#3  0x000011a92391c77d - 1
#4  0x000011a923910226 - 1
#5  0x0000000001bae523 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#6  0x0000000001b3a290 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#7  0x00000000035fc714 - 1
#8  0x0000000001b6df7f - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#9  0x0000000001c06831 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#10 0x0000000001b5f6fb - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#11 0x0000000001b387c3 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#12 0x00000000013180e1 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#13 0x0000000001319347 - 1 v8::internal::Execution::TryRunMicrotasks(v8::internal::Isolate*, v8::internal::MicrotaskQueue*, v8::internal::MaybeHandle<v8::internal::Object>*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#14 0x000000000134a7b1 - 1 v8::internal::MicrotaskQueue::RunMicrotasks(v8::internal::Isolate*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#15 0x000000000134ab5d - 1 v8::internal::MicrotaskQueue::PerformCheckpoint(v8::Isolate*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#16 0x0000000001b3baaf - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#17 0x000000000362a316 - 1
#18 0x0000000001b3889c - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#19 0x0000000001b385c3 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#20 0x0000000001317c22 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#21 0x0000000001318c84 - 1 v8::internal::Execution::Call(v8::internal::Isolate*, v8::internal::Handle<v8::internal::Object>, v8::internal::Handle<v8::internal::Object>, int, v8::internal::Handle<v8::internal::Object>*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#22 0x00000000011f6577 - 1 v8::Function::Call(v8::Local<v8::Context>, v8::Local<v8::Value>, int, v8::Local<v8::Value>*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#23 0x000000000095aa1e - 1 node::InternalCallbackScope::Close() - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#24 0x00000000011adbc9 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#25 0x0000000000ac7a6b - 1 node::StreamBase::CallJSOnreadMethod(long, v8::Local<v8::ArrayBuffer>, unsigned long, node::StreamBase::StreamBaseJSChecks) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#26 0x0000000000acdfad - 1 node::EmitToJSStreamListener::OnStreamRead(long, uv_buf_t const&) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#27 0x0000000000ad16dc - 1 node::LibuvStreamWrap::OnUvRead(long, uv_buf_t const*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#28 0x0000000000b780da - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#29 0x0000000000b842f8 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#30 0x0000000000b8abde - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#31 0x00000000011a8d48 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#32 0x000000000095a173 - 1 node::SpinEventLoop(node::Environment*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#33 0x0000000000a4802c - 1 node::NodeMainInstance::Run() - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#34 0x00000000009d0227 - 1 node::Start(int, char**) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#35 0x00007f309652a248 - 1 __libc_start_call_main - /usr/lib64/libc.so.6
    ../sysdeps/nptl/libc_start_call_main.h:58:16
#36 0x00007f309652a30b - 1 __libc_start_main_impl - /usr/lib64/libc.so.6
    ../csu/libc-start.c:360:3
#37 0x000000000094abfc - 1 _start - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
TID 59035:
#0  0x00007f309661c3f2     epoll_wait - /usr/lib64/libc.so.6
    ../sysdeps/unix/sysv/linux/epoll_wait.c:30:10
#1  0x0000000000b8add3 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#2  0x00000000011a8d48 - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#3  0x0000000000a71af9 - 1 node::WorkerThreadsTaskRunner::DelayedTaskScheduler::Start()::{lambda(void*)#1}::_FUN(void*) - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#4  0x00007f3096597fa8 - 1 start_thread - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/pthread_create.c:448:8
#5  0x00007f309661bfcc - 1 __clone3 - /usr/lib64/libc.so.6
    ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
TID 59036:
#0  0x00007f3096594bf9     __futex_abstimed_wait_common64 - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/futex-internal.c:57:12
#1  0x00007f3096594bf9     __futex_abstimed_wait_common - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/futex-internal.c:87:9
#2  0x00007f309659738e - 1 __pthread_cond_wait_common - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/pthread_cond_wait.c:426:13
#3  0x00007f309659738e - 1 ___pthread_cond_wait - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/pthread_cond_wait.c:458:10
#4  0x0000000000a7189b - 1 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/continue-binary
#5  0x00007f3096597fa8 - 1 start_thread - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/pthread_create.c:448:8
#6  0x00007f309661bfcc - 1 __clone3 - /usr/lib64/libc.so.6
    ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
... (similar threads redacted)
TID 59451:
#0  0x00007f3096619d9d     syscall - /usr/lib64/libc.so.6
    ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38
#1  0x00007f2b66e17316 - 1 tokio::runtime::scheduler::multi_thread::worker::Context::park_timeout::h670d4de74f5d5fff - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/index.node
#2  0x00007f2b66e1ff26 - 1 tokio::runtime::task::raw::poll::he07b4aa2fba1621e - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/index.node
#3  0x00007f2b66e06a7c - 1 std::sys::backtrace::__rust_begin_short_backtrace::h2254dba3da69cdcc - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/index.node
#4  0x00007f2b66e0b7e8 - 1 core::ops::function::FnOnce::call_once$u7b$$u7b$vtable.shim$u7d$$u7d$::h323612e990cf1827 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/index.node
#5  0x00007f2b66e01d0b - 1 std::sys::pal::unix::thread::Thread::new::thread_start::hcc5ed016d554f327 - /home/%REDACTED%/.local/share/JetBrains/IntelliJIdea2025.1/continue-intellij-extension/core/linux-x64/index.node
#6  0x00007f3096597fa8 - 1 start_thread - /usr/lib64/libc.so.6
    /usr/src/debug/glibc-2.40-25.fc41.x86_64/nptl/pthread_create.c:448:8
#7  0x00007f309661bfcc - 1 __clone3 - /usr/lib64/libc.so.6
    ../sysdeps/unix/sysv/linux/x86_64/clone3.S:78
... (similar threads redacted)

Edit: Here is also a thread dump auto generated by intellij during the hang: threadDump-20250611-103121_anonymized.txt

[AfterStories]

I think my issue https://github.com/continuedev/continue/issues/6110 may be related to this one.

I saw another issue with the same problem mentioned by @Patrick-Erichsen: https://github.com/continuedev/continue/issues/5774

I have tried to manually disable Autocomplete in IntelliJ setting->continue. I will observe whether this can avoid the problem of blank webview.

In addition, I have also never configured the autocomplete in config.yaml/json, but just like others guys mentioned above, IntelliJ sometimes becomes stuck

[BvdMerwe]

I have this same issue with autocomplete turned off.

[ruchernchong]

I have this same issue with autocomplete turned off.

Same here for me.

[ktssr]

I'm also facing the same issue

Freeze in EDT for 67 seconds Sampled time: 40100ms, sampling rate: 100ms, GC time: 970ms (1%), Class loading: 0%

com.intellij.diagnostic.Freeze at [email protected]/java.io.FileOutputStream.writeBytes(Native Method) at [email protected]/java.io.FileOutputStream.write(FileOutputStream.java:367) at [email protected]/java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:125) at [email protected]/java.io.BufferedOutputStream.implFlush(BufferedOutputStream.java:252) at [email protected]/java.io.BufferedOutputStream.flush(BufferedOutputStream.java:246) at [email protected]/sun.nio.cs.StreamEncoder.implFlush(StreamEncoder.java:412) at [email protected]/sun.nio.cs.StreamEncoder.lockedFlush(StreamEncoder.java:214) at [email protected]/sun.nio.cs.StreamEncoder.flush(StreamEncoder.java:201) at [email protected]/java.io.OutputStreamWriter.flush(OutputStreamWriter.java:262) at com.github.continuedev.continueintellijextension.continue.CoreMessenger.write(CoreMessenger.kt:35) at com.github.continuedev.continueintellijextension.continue.CoreMessenger.request(CoreMessenger.kt:46) at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.triggerCompletion(AutocompleteService.kt:103) at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteDocumentListener$documentChanged$$inlined$invokeLater$default$1.run(actions.kt:62) at com.intellij.openapi.application.TransactionGuardImpl.runWithWritingAllowed(TransactionGuardImpl.java:240) at com.intellij.openapi.application.TransactionGuardImpl.access$100(TransactionGuardImpl.java:25) at com.intellij.openapi.application.TransactionGuardImpl$1.run(TransactionGuardImpl.java:202) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runIntendedWriteActionOnCurrentThread$lambda$7(AnyThreadWriteThreadingSupport.kt:319) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport$$Lambda/0x000000e001c131a8.compute(Unknown Source) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteIntentReadAction$lambda$6(AnyThreadWriteThreadingSupport.kt:274) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport$$Lambda/0x000000e001568478.invoke(Unknown Source) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWithTemporaryThreadLocal(AnyThreadWriteThreadingSupport.kt:204) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteIntentReadAction(AnyThreadWriteThreadingSupport.kt:274) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runWriteIntentReadAction(AnyThreadWriteThreadingSupport.kt:222) at com.intellij.openapi.application.impl.AnyThreadWriteThreadingSupport.runIntendedWriteActionOnCurrentThread(AnyThreadWriteThreadingSupport.kt:318) at com.intellij.openapi.application.impl.ApplicationImpl.runIntendedWriteActionOnCurrentThread(ApplicationImpl.java:928) at com.intellij.openapi.application.impl.ApplicationImpl$4.run(ApplicationImpl.java:501) at com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:102) at com.intellij.util.concurrency.ChildContext$runInChildContext$1.invoke(propagation.kt:102) at com.intellij.util.concurrency.ChildContext.runInChildContext(propagation.kt:108) at com.intellij.util.concurrency.ChildContext.runInChildContext(propagation.kt:102) at com.intellij.util.concurrency.ContextRunnable.run(ContextRunnable.java:27) at com.intellij.openapi.application.impl.FlushQueue.runNextEvent(FlushQueue.java:117) at com.intellij.openapi.application.impl.FlushQueue.flushNow(FlushQueue.java:43) at com.intellij.openapi.application.impl.FlushQueue$$Lambda/0x000000e001524a90.run(Unknown Source) at java.desktop/java.awt.event.InvocationEvent.dispatch(InvocationEvent.java:318) at java.desktop/java.awt.EventQueue.dispatchEventImpl(EventQueue.java:781) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:728) at java.desktop/java.awt.EventQueue$4.run(EventQueue.java:722) at [email protected]/java.security.AccessController.executePrivileged(AccessController.java:778) at [email protected]/java.security.AccessController.doPrivileged(AccessController.java:400) at [email protected]/java.security.ProtectionDomain$JavaSecurityAccessImpl.doIntersectionPrivilege(ProtectionDomain.java:87) at java.desktop/java.awt.EventQueue.dispatchEvent(EventQueue.java:750) at com.intellij.ide.IdeEventQueue.defaultDispatchEvent(IdeEventQueue.kt:585) at com.intellij.ide.IdeEventQueue._dispatchEvent(IdeEventQueue.kt:482) at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10$lambda$9(IdeEventQueue.kt:307) at com.intellij.ide.IdeEventQueue$$Lambda/0x000000e001d7d238.compute(Unknown Source) at com.intellij.openapi.progress.impl.CoreProgressManager.computePrioritized(CoreProgressManager.java:864) at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12$lambda$11$lambda$10(IdeEventQueue.kt:306) at com.intellij.ide.IdeEventQueue$$Lambda/0x000000e0018a76f8.invoke(Unknown Source) at com.intellij.ide.IdeEventQueueKt.performActivity$lambda$3(IdeEventQueue.kt:958) at com.intellij.ide.IdeEventQueueKt$$Lambda/0x000000e0018a7db0.run(Unknown Source) at com.intellij.openapi.application.TransactionGuardImpl.performActivity(TransactionGuardImpl.java:109) at com.intellij.ide.IdeEventQueueKt.performActivity(IdeEventQueue.kt:958) at com.intellij.ide.IdeEventQueue.dispatchEvent$lambda$12(IdeEventQueue.kt:301) at com.intellij.ide.IdeEventQueue$$Lambda/0x000000e0018a7050.run(Unknown Source) at com.intellij.ide.IdeEventQueue.dispatchEvent(IdeEventQueue.kt:341) at java.desktop/java.awt.EventDispatchThread.pumpOneEventForFilters(EventDispatchThread.java:207) at java.desktop/java.awt.EventDispatchThread.pumpEventsForFilter(EventDispatchThread.java:128) at java.desktop/java.awt.EventDispatchThread.pumpEventsForHierarchy(EventDispatchThread.java:117) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:113) at java.desktop/java.awt.EventDispatchThread.pumpEvents(EventDispatchThread.java:105) at java.desktop/java.awt.EventDispatchThread.run(EventDispatchThread.java:92)

[freitasskeeled]

👋🏼 any updates on the issue? I'm trying Continue with Webstorm and it just freezes in the middle of the indexing process. (if it helps, I can add a dump/logs here)

Also, would it be possible to just run Continue indexer manually? Like a standalone script that does the first build? I'm wondering if that could be a temporary workaround at least for the initial indexing.

[exigow]

Hi @freitasskeeled 👋, thanks for reporting this! We're currently working on improving stability and doing our best to eliminate this type of freezing issues.

I have two questions:

• Which version of Continue are you using? We recently introduced some fixes that improve stability but to reproduce your issue I may need the exact number. Is this the latest version?
• I'm trying to reproduce the indexing issue but without success. Maybe the project you're working on is open source and can I try to reproduce this locally? If not, maybe can you point me to a repository that causes a similar issue?

Answering your question about indexing: the option is available in the Continue toolbar under the ⚙ icon -> Indexing tab -> Click to re-index.

[ruchernchong]

What I noticed, this is regardless of Continue's plugin version. It has to do with the major update to 2025.X.X for any of JetBrains's IDE

[freitasskeeled]

@exigow no worries, glad I can help!

Which version of Continue are you using? We recently introduced some fixes that improve stability but to reproduce your issue I may need the exact number. Is this the latest version?

I believe it is the latest available in the JetBrains Marketplace.

Continue: 1.0.21 Webstorm: 2025.1.3 Not sure if it matters but I'm running a Mac M2

I'm trying to reproduce the indexing issue but without success. Maybe the project you're working on is open source and can I try to reproduce this locally? If not, maybe can you point me to a repository that causes a similar issue?

Unfortunately, it is a private repository. I can try testing it with some open source ones.

Answering your question about indexing: the option is available in the Continue toolbar under the ⚙ icon -> Indexing tab -> Click to re-index.

Sorry, I should explained this better: would it be possible to run the initial index operation manually like through a script? The goal would be to create the initial index bypassing the current freeze that occurs with the plugin and then use the plugin for incremental updates. I saw this but I would like to avoid creating a custom implementation if possible.

[exigow]

Thanks for the answers @freitasskeeled! I reproduced your setting and I wasn’t able to trigger similar issues, but I have some ideas (more limited resources & much larger codebase).

would it be possible to run the initial index operation manually like through a script?

Unfortunately I’m not familiar with such a mechanism. Looking at sources, I found that there is a internal message called "indexing/reindex" in the protocol, but I’m not sure how to trigger it manually.

[exigow]

Just a quick heads-up: alongside debugging these issues, we're currently adding extra logging (like https://github.com/continuedev/continue/pull/6372) that will attach opt-in thread dumps in case of exceptions or any threading violations. I wanted to let you know that we’re still working on this, and ongoing fixes will be included in the upcoming release.