-
Notifications
You must be signed in to change notification settings - Fork 1
Open
Labels
bugSomething isn't workingSomething isn't working
Description
Since the update today (v0.2.0), I always got a crash of 4D-LSP.
I have tried with the Automatic download and use of tool4d: true and false. When false I have used 4D v20 R5 server
Crash with 4D v20 R5 Server :
[Error - 17:22:18] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 17:22:18] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
[Error - 17:22:18] Stopping server failed
Message: Cannot call write after a stream was destroyed
Code: -32099
Language server exited from signal SIGSEGV
Crash with Automatic download and use of tool4d: true
The 4D-LSP logs are much more verbose so I will not show all but here are some and the errors
A lot of (7000 lines of logs in 2 minutes)
[Trace - 17:27:21] Sending notification 'textDocument/didChange'.
Params: {...
[Trace - 17:27:21] Sending request 'textDocument/semanticTokens/full - (7)'.
Params: {...
[Trace - 17:27:21] Received response 'textDocument/semanticTokens/full - (7)' in 15ms.
Result: {
"data": [
0,
0,
7,
...
]
[Trace - 17:27:21] Sending notification 'textDocument/willSave'.
Params: { ...
[Trace - 17:27:21] Sending request 'textDocument/formatting - (8)'.
Params: { ...
5 times
[Info - 17:27:21] Connection to server got closed. Server will restart.
true
Language server exited from signal SIGSEGV
Then
[Error - 17:28:11] The 4D-LSP server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
Language server exited from signal SIGSEGV

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
bugSomething isn't workingSomething isn't working