In Ubuntu 18.04.4 after exiting the shell there is a gvfsd-fuse process and mounted filesystem left mounted. Normally this is fine and if a new instance of wash starts it will re-use the process / mount. However if wash exits abnormally this can create multiple zombie processes / mounts and an inability to start the shell.
Expected Behavior
Wash should cleanup these resources when it exits, or check for their existence when starting.
Steps to Reproduce
Steps to reproduce the behavior:
Start wash
Run pkill wash or similar
The shell fails to initialize, if you kill the process again you will see multiple mounts left over:
gvfsd-fuse on /run/user/1000/gvfs type fuse.gvfsd-fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /home/user/.cache/wash/mnt014415005 type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
/dev/fuse on /home/user/.cache/wash/mnt454964253 type fuse (rw,nosuid,nodev,relatime,user_id=1000,group_id=1000)
Describe the Bug
In Ubuntu 18.04.4 after exiting the shell there is a gvfsd-fuse process and mounted filesystem left mounted. Normally this is fine and if a new instance of wash starts it will re-use the process / mount. However if wash exits abnormally this can create multiple zombie processes / mounts and an inability to start the shell.
Expected Behavior
Wash should cleanup these resources when it exits, or check for their existence when starting.
Steps to Reproduce
Steps to reproduce the behavior:
pkill wash
or similarEnvironment