search

voldikss / coc-lsp-wl

See https://github.com/voldikss/coc-extensions
7 stars 0 forks source link

Dangling WolframKernel instances #5

Open oblitum opened 5 years ago

oblitum commented 5 years ago

When I close (Neo)Vim, the WolframKernel instance started by the editor is left dangling when the editor is closed. The WolframKernel instances keep accumulating and the fix I know of is to killall -9.

I've asked whether the plugin has to do something in particular to close the instances in this original issue:

kenkangxgwe commented 4 years ago

HI, could you

  1. Enable logging.
  2. Open a wolfram code file and close the editor after the kernel is up.
  3. Paste the logs here.

Thanks

oblitum commented 4 years ago

Hi @kenkangxgwe. Simply opening and closing the file sometimes makes it not happen, I think I had to move the cursor and close, so the issue happens almost always, but not always, this is the log (I had killed WolframKernel in the end):

[DEBUG 2020-03-09T12:20:34] Logging level: DEBUG
[INFO  2020-03-09T12:20:34] Initializing Wolfram Language Server
[INFO  2020-03-09T12:20:35] Language server is connecting the client through
socket.
[INFO  2020-03-09T12:20:35] Server listening from port 6536...
[DEBUG 2020-03-09T12:20:36] handle/initialize
[INFO  2020-03-09T12:20:36] {CheckUpgrades, Quantity[0.034054, "Seconds"]}
[DEBUG 2020-03-09T12:20:36] 4
[DEBUG 2020-03-09T12:20:52] Close Document
file:///home/francisco/Projects/samples/mathematica/sample.wl
VasilySotnikov commented 4 years ago

Are there any updates regarding this issue or a known (automatic) workaround? I observe the same bug on Linux. The WolframKernel instance is almost never closed.