GoLand does not alway close

Answered

I noticed a few times that I could not start GoLand. It ended up being a zombie process still running (no frontend).

It seems that this mostly happens when I terminate a running job while closing GoLand.

Is there something I can do to help to debug the IDE?

EDIT: I just noticed that GoLand asked me twice to terminate a running npm script (quasar dev), after what the IDE closed but the process is still there.

6 comments
Comment actions Permalink

Let's start with the IDE logs. You can collect them via Help | Collect Logs and Diagnostic Data and upload them to https://uploads.jetbrains.com/, then provide its ID. Do I get it correctly that you cannot start the GoLand instance? Do you have GoLand/other IDEs open at the same time?

EDIT: I just noticed that GoLand asked me twice to terminate a running npm script (quasar dev), after what the IDE closed but the process is still there.

Does it happen after a few minutes after the IDE closing? By the way, you can configure a default behavior in the settings: Preferences | Appearance & Behavior | System Settings.

0
Comment actions Permalink

Let's start with the IDE logs

I uploaded the file and the ID is 2021_09_09_UTyJqMya3RyZMWJV

Do you want me to gather the logs at a specific time?

Do I get it correctly that you cannot start the GoLand instance? 

Yes, this is how I discovered that there is a problem. After killing the GoLand process via the task manager I can start fine. I did not have any other IDE started at that time.

Does it happen after a few minutes after the IDE closing? By the way, you can configure a default behavior in the settings: Preferences | Appearance & Behavior | System Settings.

No, it happens right after the IDE closes. I have configured it to ask before terminating a process (and I chose "terminate" when asked).

As far as I can tell (I can do more experiments if needed), it happens when closing an npm process, and not a go one.

 
0
Comment actions Permalink

No, it happens right after the IDE closes. I have configured it to ask before terminating a process (and I chose "terminate" when asked).

If you still leave a process for a while after the IDE closing, how much time does it take to finish and close the process, or it cannot be finished at all? How soon are you starting the IDE? Does it make a difference if you first close all the projects using File | Close All Projects action and then exit the IDE?

Do you want me to gather the logs at a specific time?

The current one is fine, thank you.

0
Comment actions Permalink

OK, I pinpointed the problem in a reproducible way. I have a project that has a Go backend and a Quasar (Vue.js, typescript) frontend. I start them together (via the "compound run") and tried to close (and be asked to terminate the process) when the back was running alone, and then when the front was running alone.

  • When closing the IDE running only the back, and terminating the Go process everything is fine.
  • When closing the IDE running only the front, I am asked at IDE closure to terminate the front (= an npm process), the IDE closes and I am asked again to terminate the front. This leaves a zombie GoLand process.

If you still leave a process for a while after the IDE closing, how much time does it take to finish and close the process, or it cannot be finished at all? 

It does not finish on its own, I have to kill it via Task Manager.

How soon are you starting the IDE? 

Not sure I understand. How soon after a reboot? Not particularly soon, the OS is stabilized. How soon after closing the previous one? I wanted to do it immediately, and then after some time - but ultimately the GoLand process blocks it and that process does not end ever (I had a case when I closed the IDE, that left the zombie process, and I tried to restart it after an hour)

Does it make a difference if you first close all the projects using File | Close All Projects action and then exit the IDE?

Ah yes, it does! Good catch! I get one prompt to terminate the npm process, get back to the project chooser, then close the IDE - and there is no process left behind.

It indeed looks like the "ask to terminate when the IDE is being closed" kind of process that has the issue.

0
Comment actions Permalink

Thanks for your detailed report and steps to reproduce. Indeed, I've managed to reproduce it as well.

Could you please confirm that it works as expected on the Nightly version of GoLand? You can download it via Toolbox App.

0
Comment actions Permalink

Could you please confirm that it works as expected on the Nightly version of GoLand? 

Yes, I cannot reproduce the error with Nightly. Thank you!

0

Please sign in to leave a comment.