@equalsraf

True but if you need secure (as in confidential/authenticated) remote TCP connections to neovim you really should use existing tools like ssh or stunnel, instead of implementing them here. Sidenote:...

Strange the tests were supposed to use the deja vu ttf fonts in the third-party folder.

I was seeing a similar issue in Linux/X11 with an intel card. I changed the hi-dpi value in settings.json to false, and was able to avoid the issue. ```json "hiDPI":...

That function should already be calling `m_shell->close()` which would result in a call to the Shell class ```c++ void Shell::closeEvent(QCloseEvent *ev) { if (m_attached && m_nvim->connectionType() == NeovimConnector::SpawnedConnection) { //...

I've tried to reproduce this earlier, but no luck so far. In my case I was running python, but all processes terminated when I closed. It might be worth trying...

Maybe some plugin is preventing it from shutting down properly. It is strange that the window is closing though. That would mean this function is being called but nvim does...

So coc_nvim is the only one there - https://github.com/neoclide/coc.nvim/blob/79e9e048dfedbfc8b91330059fec5470f8b68f14/plugin/coc.vim#L328 - https://github.com/neoclide/coc.nvim/blob/79e9e048dfedbfc8b91330059fec5470f8b68f14/plugin/coc.vim#L276 - https://github.com/neoclide/coc.nvim/blob/9a438d919a4128fad30e5a05da0987ff0598c676/autoload/coc/rpc.vim#L186 Tricky to track past that point. Just to confirm and narrow it down, can you try disabling...

Ok I've come across something that might be related to this one. See https://github.com/equalsraf/neovim-qt/pull/1076 for a possible fix. Although we might become too aggressive in killing the processes.

The tests are causing our windows builds to fail :S, here is a working one https://ci.appveyor.com/project/equalsraf/neovim-qt/builds/47679296/job/7rc7nmxjxw5rb8ex/artifacts

We don't really have a path forward here. Closing. But feel free to open issues with good approaches that improve this.