Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Latest version of Continue (0.0.85) crashes Jetbrains Webstorm #3709

Open
3 tasks done
scpedicini opened this issue Jan 13, 2025 · 9 comments
Open
3 tasks done

Latest version of Continue (0.0.85) crashes Jetbrains Webstorm #3709

scpedicini opened this issue Jan 13, 2025 · 9 comments
Assignees
Labels
area:indexing Relates to embedding and indexing ide:jetbrains Relates specifically to JetBrains extension kind:bug Indicates an unexpected problem or unintended behavior priority:highest Indicates the highest possible priority

Comments

@scpedicini
Copy link

scpedicini commented Jan 13, 2025

Before submitting your bug report

Relevant environment info

- OS: Apple M1 Max Sonoma 14.7.1 (23H222)
- Continue version: 0.0.85
- IDE version: Webstorm 2024.3.1.1 
- config.json:
  
{
  "models": [
    {
      "model": "claude-3-5-sonnet-latest",
      "contextLength": 200000,
      "title": "Claude 3.5 Sonnet",
      "apiKey": "*********************",
      "provider": "anthropic"
    }
  ],
  "tabAutocompleteModel": {
    "title": "Starcoder2 3b",
    "provider": "ollama",
    "model": "starcoder2:3b"
  }
}

Description

With the latest version of the Continue plugin, any attempt to add/modify code in any repository in the regular IDE completely freezes up - requiring a bash kill command to recover. Uninstalling/Reinstalling the plugin from scratch had no effect.

Only workaround is to completely disable the Continue plugin or revert back to 0.0.83.

To reproduce

No response

Log output

[info] Starting Continue core...
[2025-01-13T16:29:58] [info] Starting Continue core... 
[2025-01-13T16:29:58] Setup 
[2025-01-13T16:29:58] [binary] Core started 
[2025-01-13T16:29:58] error when indexing:  Error: Failed to generate embeddings for 12 chunks with provider: A::all-MiniLM-L6-v2::500: Error: `local_files_only=true` or `env.allowRemoteModels=false` and file was not found locally at "/snapshot/continue/binary/models/all-MiniLM-L6-v2/tokenizer.json".
[2025-01-13T16:29:58] Indexing failed with error:  Error: Failed to generate embeddings for 12 chunks with provider: A::all-MiniLM-L6-v2::500: Error: `local_files_only=true` or `env.allowRemoteModels=false` and file was not found locally at "/snapshot/continue/binary/models/all-MiniLM-L6-v2/tokenizer.json". gle.getEmbeddings, async gle.computeRows, async gle.update, async _gA.indexFiles, async _gA.refreshDirs, async jgA.refreshCodebaseIndex
@dosubot dosubot bot added area:indexing Relates to embedding and indexing ide:jetbrains Relates specifically to JetBrains extension kind:bug Indicates an unexpected problem or unintended behavior priority:highest Indicates the highest possible priority labels Jan 13, 2025
@ritamariavermelho06
Copy link

Same here using Intellij!

@mgzob
Copy link

mgzob commented Jan 14, 2025

I'm experiencing the same thing.

At risk of misdiagnosing it seems to be related to autocompletions. Like @scpedicini , the crash occurs when inserting new text and does not occur until new code is written in the window. Here's a log snippet from the threadDump:

"AWT-EventQueue-0" prio=0 tid=0x0 nid=0x0 waiting on condition
     java.lang.Thread.State: WAITING
 on java.util.concurrent.FutureTask@495573ae
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:221)
	at [email protected]/java.util.concurrent.FutureTask.awaitDone(FutureTask.java:500)
	at [email protected]/java.util.concurrent.FutureTask.get(FutureTask.java:190)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.isInjectedFile(AutocompleteService.kt:306)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.clearCompletions(AutocompleteService.kt:290)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.clearCompletions$default(AutocompleteService.kt:289)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteCaretListener.caretPositionChanged(AutocompleteEditorListener.kt:28)
	at [email protected]/java.lang.invoke.LambdaForm$DMH/0x00000176214a8c00.invokeInterface(LambdaForm$DMH)

It lists a blocking event with com.intellij.codeWithMe:

---------- Coroutine dump (stripped) ----------
 
 - BlockingCoroutine{Active}@1ee580c3 [BlockingEventLoop@7e8b4d5a]
 	- "Application":supervisor:ChildScope{Active}
 		- "ApplicationImpl@1683170907 container":supervisor:ChildScope{Active} [ComponentManager(ApplicationImpl@1683170907), com.intellij.codeWithMe.ClientIdContextElementPrecursor@27b15c4d]
 			- "(ApplicationImpl@1683170907 x com.intellij.platform.ide.provisioner)":supervisor:ChildScope{Active} [ComponentManager(ApplicationImpl@1683170907), com.intellij.codeWithMe.ClientIdContextElementPrecursor@27b15c4d]

If I disable the codeWithMe builtin, code completion does not work but the crash is delayed. IIRC from yesterday it did still crash though.

My exploration was small though so I don't know how much use the above snippets are.

My environment is:

  • OS: Win 10 22H2 amd x86
  • Continue version: 0.0.85
  • IDE version: Intellij Idea 2024.3.1.1

@AfterStories
Copy link

AfterStories commented Jan 14, 2025

Same , Latest main branch

OS: Win 10
Continue version: 0.0.85
IDE version: Intellij Idea 2024.3.1.1

I saw the comment above that the program was blocked during debug .I am not debugging the local code, but packaging it as an installation package and testing it after installation

When I open IntelliJ and use the plugin, it works fine for the first few minutes. After a few minutes, when I type any text in any file, IntelliJ will crash. If you don't enter any characters, it won't crash.
When I uninstalled the plugin, IntelliJ ran good ,

So it is obvious that the existence of the continue plugin caused IntelliJ to crash ,this issue author is
@scpedicini ,you cans see he use mac , and I use windows computer,It seems that different systems will have the same problem

I hope continue team can solve it quickly. This problem has already made it impossible to use IntelliJ normally.
image

@AfterStories
Copy link

AfterStories commented Jan 14, 2025

After many tests: when it gets stuck and crashes, I I killed IntelliJ using Task Manager , restart IntelliJ and uninstall the plugin, install it again, and it works for a while. I'm not sure how long this work period is. ....now, it has work for 0.5 hour and I can still type. But sometimes, I only use it for 10 minutes then try to input text in the file , it will crash.

issue in discord : https://discord.com/channels/1108621136150929458/1157097395235082361/threads/1328695016763293796

@rayanbzd
Copy link

Tried 0.0.85 today,

IntelliJ 2024.3.3.1
MacOS Sequoia 15.1.1

Crash immediatly on text input on any file
Even with autocomplete feature disabled

Tried to uninstall and reinstall, full reset of the .continue folder to make sure its a clean install.
Still crashing totally the IDE.

@rayanbzd
Copy link

I'm experiencing the same thing.

At risk of misdiagnosing it seems to be related to autocompletions. Like @scpedicini , the crash occurs when inserting new text and does not occur until new code is written in the window. Here's a log snippet from the threadDump:

"AWT-EventQueue-0" prio=0 tid=0x0 nid=0x0 waiting on condition
     java.lang.Thread.State: WAITING
 on java.util.concurrent.FutureTask@495573ae
	at [email protected]/jdk.internal.misc.Unsafe.park(Native Method)
	at [email protected]/java.util.concurrent.locks.LockSupport.park(LockSupport.java:221)
	at [email protected]/java.util.concurrent.FutureTask.awaitDone(FutureTask.java:500)
	at [email protected]/java.util.concurrent.FutureTask.get(FutureTask.java:190)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.isInjectedFile(AutocompleteService.kt:306)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.clearCompletions(AutocompleteService.kt:290)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteService.clearCompletions$default(AutocompleteService.kt:289)
	at com.github.continuedev.continueintellijextension.autocomplete.AutocompleteCaretListener.caretPositionChanged(AutocompleteEditorListener.kt:28)
	at [email protected]/java.lang.invoke.LambdaForm$DMH/0x00000176214a8c00.invokeInterface(LambdaForm$DMH)

It lists a blocking event with com.intellij.codeWithMe:

---------- Coroutine dump (stripped) ----------
 
 - BlockingCoroutine{Active}@1ee580c3 [BlockingEventLoop@7e8b4d5a]
 	- "Application":supervisor:ChildScope{Active}
 		- "ApplicationImpl@1683170907 container":supervisor:ChildScope{Active} [ComponentManager(ApplicationImpl@1683170907), com.intellij.codeWithMe.ClientIdContextElementPrecursor@27b15c4d]
 			- "(ApplicationImpl@1683170907 x com.intellij.platform.ide.provisioner)":supervisor:ChildScope{Active} [ComponentManager(ApplicationImpl@1683170907), com.intellij.codeWithMe.ClientIdContextElementPrecursor@27b15c4d]

If I disable the codeWithMe builtin, code completion does not work but the crash is delayed. IIRC from yesterday it did still crash though.

My exploration was small though so I don't know how much use the above snippets are.

My environment is:

* OS: Win 10 22H2 amd x86

* Continue version: 0.0.85

* IDE version: Intellij Idea 2024.3.1.1

Even when autocompletion feature disabled it still crash.
Is autocompletion still doing some things in background even if its disabled ?

@chubshaun
Copy link

Is autocompletion still doing some things in background even if its disabled ?

I'd like to know the answer to this as well. I just noticed that my config.json has this:

  "tabAutocompleteModel": {
    "title": "Starcoder2 3b",
    "provider": "ollama",
    "model": "starcoder2:3b"
  }

I do have ollama but this model is not installed, and I don't make use of Continue's TAB autocomplete. I'm wondering if I should delete that block from my config.json altogether.

@tomasz-stefaniak
Copy link
Collaborator

tomasz-stefaniak commented Jan 14, 2025

Just a heads-up that we are working on fixing this. We're also going to make changes to our CI/CD pipeline to specifically screen for critical bugs on Jetbrains on Windows to prevent avoidable problems like this from happening in the future.

@Patrick-Erichsen
Copy link
Collaborator

Hi all, #3726 should resolve the issue. A recent change that attempted to resolve a latency issue with autocomplete logic had caused an unintended block on the main Event Dispatch Thread (EDT) in JetBrains.

We will publish 0.0.86 tonight with this fix, and are spending time this week polishing our CI/CD around JetBrains across Windows, Linux, and macOS as @tomasz-stefaniak outlined 👍

Improving stability of JB is high on our priority list going forwards based on this event and other regressions over the past month or two. Appreciate everyone's patience as we move towards that goal!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area:indexing Relates to embedding and indexing ide:jetbrains Relates specifically to JetBrains extension kind:bug Indicates an unexpected problem or unintended behavior priority:highest Indicates the highest possible priority
Projects
None yet
Development

No branches or pull requests

8 participants