Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zombie processes remain in workspace container after a task is terminated. #22772

Closed
akurinnoy opened this issue Jan 18, 2024 · 2 comments
Closed
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.

Comments

@akurinnoy
Copy link
Contributor

Describe the bug

While working in che-code, I encountered a lot of processes labeled <defunct> in my workspace container. I noticed that every time a devfile task or corresponding yarn script gets terminated, one or more zombie processes appear.

Che version

next (development version)

Steps to reproduce

  1. Clone repository git@github.com:eclipse-che/che-dashboard.git
  2. Run the task "Install dependencies".
  3. Open the terminal and run the top command (and hit c to see more than just the command name). You may see some zombie processes at this point.
  4. Split the terminal, run yarn build, and terminate it in a minute.
    • Alternatively, run the "build" task, and terminate it in a minute.
  5. In the terminal where the top command runs, you can see a few more zombie processes.
  6. You can try steps 4-5 with other tasks, e.g. "watch frontend", and "watch backend".

Expected behavior

No zombie processes should remain after a task termination.

Runtime

OpenShift

Screenshots

https://youtu.be/yWVRiQFYfxs

Steps to reproduce

Installation method

other (please specify in additional context)

Environment

other (please specify in additional context)

Eclipse Che Logs

No response

Additional context

No response

@akurinnoy akurinnoy added the kind/bug Outline of a bug - must adhere to the bug report template. label Jan 18, 2024
@che-bot che-bot added the status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. label Jan 18, 2024
@ibuziuk ibuziuk added sprint/next team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs. labels Jan 18, 2024
@amisevsk amisevsk added severity/P2 Has a minor but important impact to the usage or development of the system. and removed status/need-triage An issue that needs to be prioritized by the curator responsible for the triage. See https://github. labels Jan 20, 2024
@vitaliy-guliy
Copy link
Contributor

I got the same when I played with ssh service. I've just started and stopped it several times by a command in terminal

Screenshot from 2024-01-22 16-48-26

@vitaliy-guliy
Copy link
Contributor

I've just double checked it on the dogfooding instance and haven't faced any issues anymore.
No zombie processes appeared after running yarn install command.
I tried to launched yarn in both VS Code terminal and in the OpenShift console terminal. In both cases it was successful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Outline of a bug - must adhere to the bug report template. severity/P2 Has a minor but important impact to the usage or development of the system. sprint/next team/B This team is responsible for the Web Terminal, the DevWorkspace Operator and the IDEs.
Projects
None yet
Development

No branches or pull requests

5 participants