-
Notifications
You must be signed in to change notification settings - Fork 446
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
extension has problem activating most of the time #3901
Comments
@mkgarn Could you, please, try VS Code 1.40.0 ? |
@snjeza , when did this regress ? Update: Is it really eclipse-jdtls/eclipse.jdt.ls#3296 ? |
@rgrunber You can also look at eclipse-jdtls/eclipse.jdt.ls#2319 |
I was able to reproduce this with reloading spring-petclinic : !ENTRY org.eclipse.osgi 2 0 2025-01-15 09:11:15.466
!MESSAGE While loading class "org.eclipse.buildship.core.internal.preferences.PersistentModelConverter$10", thread
"Thread[#38,Worker-2: Load persistent model for all projects,5,main]" timed out waiting (30019ms) for thread
"Thread[#36,Worker-1: Initialize After Load,5,main]" to finish starting bundle
"org.eclipse.buildship.core_3.1.10.v20250114-0428-s [22]". To avoid deadlock, thread "Thread[#38,Worker-2: Load persistent
model for all projects,5,main]" is proceeding but
"org.eclipse.buildship.core.internal.preferences.PersistentModelConverter$10" may not be fully initialized. !MESSAGE While loading class "org.eclipse.buildship.core.internal.CorePlugin", thread "Thread[#43,Worker-4: Initialize
Workspace,5,main]" timed out waiting (30016ms) for thread "Thread[#36,Worker-1: Initialize After Load,5,main]" to finish
starting bundle "org.eclipse.buildship.core_3.1.10.v20250114-0428-s [22]". To avoid deadlock, thread
"Thread[#43,Worker-4: Initialize Workspace,5,main]" is proceeding but "org.eclipse.buildship.core.internal.CorePlugin"
may not be fully initialized. |
@rgrunber eclipse-jdtls/eclipse.jdt.ls#3357 should fix it |
It would be good if @mkgarn could let us know if this improves the situation (fix is in the vscode-java pre-release builds, or by trying the vsix referenced above). The only thing I could confirm is that this eliminates some possible deadlocks. |
Type: Bug
This extension sits in the Activating state for ever and never activates. I do not know how to fix this. It seems to work some times, but not consistently across apps.
Extension version: 1.37.0
VS Code version: Code 1.94.2 (384ff7382de624fb94dbaf6da11977bba1ecd427, 2024-10-09T16:08:44.566Z)
OS version: Windows_NT x64 10.0.22631
Modes:
Remote OS version: Linux x64 5.14.0-427.42.1.el9_4.x86_64
Remote OS version: Linux x64 5.14.0-427.42.1.el9_4.x86_64
System Info
canvas_oop_rasterization: enabled_on
direct_rendering_display_compositor: disabled_off_ok
gpu_compositing: enabled
multiple_raster_threads: enabled_on
opengl: enabled_on
rasterization: enabled
raw_draw: disabled_off_ok
skia_graphite: disabled_off
video_decode: enabled
video_encode: enabled
vulkan: disabled_off
webgl: enabled
webgl2: enabled
webgpu: enabled
webnn: disabled_off
A/B Experiments
The text was updated successfully, but these errors were encountered: