*** This bug is a duplicate of bug 1864901 ***
https://bugs.launchpad.net/bugs/1864901
Yes, and this is being tracked in bug #1864901, so I'm marking as a
duplicate. This should be fixed in the stable channel, by the way.
** This bug has been marked a duplicate of bug 1864901
[snap] suggestion: alert users when the snap has been refreshed while running
--
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/1874973
Title:
New, never-ending chromium.launcher process on every chromium start
since [Focal 20.04/Snap] due to check_current_symlink()
Status in chromium-browser package in Ubuntu:
New
Bug description:
Since my upgrade from 19.10 to 20.04 on every start a _new_
/snap/chromium/[digit]/bin/chromium.launcher instance is launched and
never-ending. It spawns a "sleep 60" child process.
Five time starting (and stopping!) chromium = 5 processes
2823981 ? S 0:00 \_ /bin/sh
/snap/chromium/1119/bin/chromium.launcher
2832707 ? S 0:00 | \_ sleep 60
2824647 ? S 0:00 \_ /bin/sh
/snap/chromium/1119/bin/chromium.launcher
2831803 ? S 0:00 | \_ sleep 60
2825134 ? S 0:00 \_ /bin/sh
/snap/chromium/1119/bin/chromium.launcher
2831953 ? S 0:00 | \_ sleep 60
2825521 ? S 0:00 \_ /bin/sh
/snap/chromium/1119/bin/chromium.launcher
2832057 ? S 0:00 | \_ sleep 60
2832767 ? S 0:00 \_ /bin/sh
/snap/chromium/1119/bin/chromium.launcher
2832771 ? S 0:00 \_ sleep 60
The sleep 60 clearly indicates a problem in the
check_current_symlink() function.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1874973/+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
