It also occurs with a freshly installed chromium. It can be easily reproduced:
``` $ pgrep chromium | xargs kill # kill any running chromium (beware!) $ pgrep chromium | wc -l 0 # There are non running $ /snap/bin/chromium --product-version # command quits immediately. $ pgrep chromium | wc -l 1 $ /snap/bin/chromium # opens a browser. # Quit browser manually. $ pgrep chromium | wc -l 2 $ ps faux | grep chromium # check any processes running. \_/bin/sh /snap/chromium/1100/bin/chromium.launcher --product-version \_/bin/sh /snap/chromium/1100/bin/chromium.launcher ``` This shows that a process remains active after closing or running. The `ps faux` shows the leftover running processes and clearly shows they no longer have a parent: it seems the parent process forks, then quits, but leaves its child running. Above comment comes from a bug that this behaviour introduced in a project that uses chrome: https://github.com/titusfortner/webdrivers/issues/168 So, besides it leaving around running processes (slightly messy), it causes bugs (hanging) in scripts and tools that wait for chrome+children to exit. ** Bug watch added: github.com/titusfortner/webdrivers/issues #168 https://github.com/titusfortner/webdrivers/issues/168 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1864901 Title: [snap] suggestion: alert users when the snap has been refreshed while running Status in chromium-browser package in Ubuntu: Triaged Bug description: When the chromium snap is being automatically refreshed to a newer revision while the app is running, undefined behaviour might happen, as well as data loss (because the profile folder is versioned). This issue is regularly being reported (see e.g. the duplicates of bug #1616650). Jamie has an interesting suggestion to mitigate this situation, until refresh app awareness becomes default: « […] it would be possible for you to run something in the background that could occasionally see if the current symlink changed, and then alert to restart whenever refresh app awareness lands, it could be converted to see if something is pending, if so, prompt/alert to stop to have updates applied, or something simple idea is to nohup a script in a wrapper before invoking chromium proper iirc, firefox used to have UX built into it letting the user know it needed to be restarted, so there is some precedent for this sort of thing » To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1864901/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : [email protected] Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
