redhat-developer / redhat-developer/vscode-java

server shutdown

Open
#3,685 3 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
2.3k
Forks
546
Avg merge
20h 1m
Merged PRs (30d)
11

Description

Type: Bug

Open vscode normally, then wait
Crash report:
[Trace - 09:10:41] Sending request 'shutdown - (23)'.
[Trace - 09:10:41] Received response 'shutdown - (23)' in 150ms.
Result: {}

[Trace - 09:10:41] Sending notification 'exit'.
No parameters provided.

Extension version: 1.31.0
VS Code version: Code 1.90.2 (5437499feb04f7a586f677b155b039bc2b3669eb, 2024-06-18T22:34:26.404Z)
OS version: Windows_NT x64 10.0.19045
Modes:
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2
Remote OS version: Linux x64 5.15.146.1-microsoft-standard-WSL2

System Info
Item Value
CPUs Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 2712)
GPU Status 2d_canvas: enabled
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
Load (avg) undefined
Memory (System) 15.94GB (3.66GB free)
Process Argv --folder-uri vscode-remote://wsl%2Bdebian/home/mobius/work/shihuan-multimedia-ui --crash-reporter-id dc2a9fc6-7d55-4fa3-9be5-45db5215ed52
Screen Reader no
VM 0%
Item Value
Remote WSL: Debian
OS Linux x64 5.15.146.1-microsoft-standard-WSL2
CPUs Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 0)
Memory (System) 7.76GB (1.89GB free)
VM 0%
Item Value
Remote WSL: Debian
OS Linux x64 5.15.146.1-microsoft-standard-WSL2
CPUs Intel(R) Core(TM) i5-6400 CPU @ 2.70GHz (4 x 0)
Memory (System) 7.76GB (1.89GB free)
VM 0%
A/B Experiments
vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscorecescf:30445987
vscod805cf:30301675
binariesv615:30325510
vsaa593cf:30376535
py29gd2263:31024239
c4g48928:30535728
azure-dev_surveyone:30548225
2i9eh265:30646982
962ge761:30959799
pythongtdpath:30769146
pythonnoceb:30805159
asynctok:30898717
pythonregdiag2:30936856
pythonmypyd1:30879173
h48ei257:31000450
pythontbext0:30879054
dsvsc016:30899300
dsvsc017:30899301
dsvsc018:30899302
cppperfnew:31000557
dsvsc020:30976470
pythonait:31006305
jchc7451:31067544
dsvsc021:30996838
bdiig495:31013172
pythoncenvpt:31062603
a69g1124:31058053
dvdeprecation:31068756
dwnewjupyter:31046869
legacy_priority:31082724

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

The report identifies a shutdown request and exit notification in VS Code 1.90.2 with the Java extension running remotely on WSL Debian, but names no source file, test, or entry point. Start by reproducing the shutdown after opening the project under WSL and inspect the extension and language-server logs. Done means identifying the cause and demonstrating that the server no longer shuts down unexpectedly.

Written by the indexing model from the issue text.

Assessment

Tech stack
java, linux, typescript, vscode
Domain
developer-experience, tooling
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
20/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.