nextcloud / nextcloud/whiteboard
Whiteboard docker container with a lot of zombie processes
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 215
- Forks
- 39
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 32
Description
Hello Devs!
Although the app seems to work fine, on the host the docker container runs on, are a lot of zombie processes. They pile up the more one uses the app in nextcloud.
root@misc:~/nextcloud-whiteboard-docker# ps auxww | grep Z
USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND
nobody 5022 0.0 0.0 0 0 ? Z 10:03 0:00 [chrome_crashpad] <defunct>
nobody 5024 0.0 0.0 0 0 ? Z 10:03 0:00 [chrome_crashpad] <defunct>
nobody 5026 0.0 0.0 0 0 ? Z 10:03 0:00 [chromium] <defunct>
nobody 5027 0.0 0.0 0 0 ? Z 10:03 0:00 [chromium] <defunct>
root 5593 0.0 0.0 6544 2392 pts/1 S+ 10:10 0:00 grep --color=auto Z
root@misc:~/nextcloud-whiteboard-docker#
Within the docker container I see the same:
Mem: 2316660K used, 5815120K free, 6040K shrd, 62052K buff, 1186688K cached
CPU: 0% usr 0% sys 0% nic 98% idle 0% io 0% irq 0% sirq
Load average: 0.02 0.08 0.03 2/452 465
PID PPID USER STAT VSZ %VSZ CPU %CPU COMMAND
18 1 nobody S 1121m 14% 3 0% {node-MainThread} node websocket_server/main.js
1 0 nobody S 1112m 14% 1 0% npm run server:start
443 0 nobody S 1708 0% 0 0% /bin/sh
465 443 nobody R 1636 0% 3 0% top
54 1 nobody Z 0 0% 0 0% [chromium]
55 1 nobody Z 0 0% 3 0% [chromium]
52 1 nobody Z 0 0% 2 0% [chrome_crashpad]
50 1 nobody Z 0 0% 0 0% [chrome_crashpad]
I guess that's not how it is supposed to be, right?
cheers!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the issue while monitoring processes both on the Docker host and inside the container with the commands shown in the report. Trace the chromium and chrome_crashpad processes and their parents; done means repeated app use no longer leaves zombie processes accumulating in either process listing.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, javascript
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 42/100