You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I get the same behaviour. Occassionally there is a traceback like this:
[Error - 7:57:44 AM] Unhandled Rejection at promise: [object Promise], reason: RuntimeError: memory access out of bounds
at wasm://wasm/000b9962:wasm-function[257]:0x2af35
at Parser.parse (/home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/web-tree-sitter/tree-sitter.js:2068:17)
at Analyzer.analyze (/homeniklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/analyser.js:47:34)
at BashServer.<anonymous> (/home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/server.js:258:45)
at Generator.next (<anonymous>)
at /home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/server.js:8:71
at new Promise (<anonymous>)
at __awaiter (/home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/server.js:4:12)
at BashServer.analyzeAndLintDocument (/home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/server.js:255:16)
at /home/niklas/.vscode/extensions/mads-hartmann.bash-ide-vscode-1.43.0/node_modules/bash-language-server/out/server.js:126:22
Code editor
Visual Studio Code
Platform
Fedora 41
Version
1.43.0
What steps will reproduce the bug?
Click on a bash/shell script
How often does it reproduce? Is there a required condition?
Non stop when you do anything.
What is the expected behavior?
No error message
What do you see instead?
[Error - 4:20:37 PM] Request textDocument/documentHighlight failed.
Message: Request textDocument/documentHighlight failed with message: memory access out of bounds
Code: -32603
Additional information
No response
The text was updated successfully, but these errors were encountered: