Language server crash

Nessuno ha ancora preso questa issue.

Type: Bug

Crash call stack:

A C/C++ extension process has crashed. The crashing process name, date/time, signal, and call stack are below -- it would be helpful to include that in a bug report at https://github.com/Microsoft/vscode-cpptools/issues.

cpptools
6/10/2025, 1:24:33 PM
SIGBUS
…
…
…
sqlite3_step+1440
…
code_store::results_statement<code_store::code_items_set_t, code_store::schema::code_items::read_statement_t, code_store::code_items_set>::count_rows(long&)+142
CExtResults<CExtCodeItemResults, CCodeItem, code_store::code_items_set, ICodeItemResults>::CountRows()+85
documentation_comment::can_generate_doxygen_comment(std::shared_ptr<msvc::file_buffer_snap_t> const&, std::string const&, bool, bool, bool, msvc::strong_typedef<msvc::line0_traits>, bool&, msvc::text_address0_t&, msvc::text_address0_t&, msvc::strong_typedef<msvc::line0_traits>&)+781
cpptools_context::cpptools_codeActionsRequest(GetCodeActionsRequestParams&&, unsigned int)+2966
…
msvc::thread_manager_t::queue_item<msvc::deque_thread<std::function<void ()>>::defer(std::function<void ()>&&)::{lambda()#1}>::operator()()+297
msvc::thread_manager_t::do_work(unsigned int)+431

Extension version: 1.25.3
VS Code version: Code 1.100.2 (848b80aeb52026648a8ff9f7c45a9b0a80641e2e, 2025-05-14T21:47:40.416Z)
OS version: Windows_NT x64 10.0.26100
Modes:
Remote OS version: Linux x64 4.18.0-553.51.1.el8_10.x86_64

System Info

Item	Value
CPUs	12th Gen Intel(R) Core(TM) i7-12700F (20 x 2112)
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 webnn: disabled_off
Load (avg)	undefined
Memory (System)	31.76GB (18.26GB free)
Process Argv	--crash-reporter-id b1511c9a-31e6-4c01-b6d6-c4c8a02f1dc9
Screen Reader	no
VM	0%

Item	Value
Remote	SSH: login
OS	Linux x64 4.18.0-553.51.1.el8_10.x86_64
CPUs	Intel(R) Xeon(R) Platinum 8351N CPU @ 2.40GHz (72 x 3282)
Memory (System)	502.72GB (451.27GB free)
VM	0%

A/B Experiments

vsliv368:30146709
vspor879:30202332
vspor708:30202333
vspor363:30204092
vscod805cf:30301675
binariesv615:30325510
c4g48928:30535728
azure-dev_surveyone:30548225
a9j8j154:30646983
962ge761:30959799
2e7ec940:31000449
pythontbext0:30879054
cppperfnew:31000557
dwnewjupytercf:31046870
pythonrstrctxt:31112756
nativeloc1:31192215
5fd0e150:31155592
dwcopilot:31170013
6074i472:31201624
dwoutputs:31242946
customenabled:31248079
9064b325:31222308
copilot_t_ci:31222730
e5gg6876:31282496
pythoneinst12:31285622
bgtreat:31268568
4gafe986:31271826
c7cif404:31314491
996jf627:31283433
pythonrdcb7:31303018
usemplatestapi:31297334
0aa6g176:31307128
7bj51361:31289155
747dc170:31275177
pylancecolor:31314202
aj953862:31281341
generatesymbolt:31295002
convertfstringf:31295003
gendocf:31295004

Inizia dallo stack del crash di cpptools segnalato, in particolare sqlite3_step, code_store::results_statement e documentation_comment::can_generate_doxygen_comment. Riproduci il SIGBUS nell’ambiente Linux remoto e VS Code indicato, quindi verifica che l’elaborazione di code-actions non causi più crash; il report non indica alcun file sorgente né alcun test di regressione.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

Guida per i contributori

Come iniziare

Direzione di ricerca

Valutazione