[Expired for snapd because there has been no activity for 60 days.]
** Changed in: snapd
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687507
Title:
Memory lea
[Expired for systemd (Ubuntu) because there has been no activity for 60
days.]
** Changed in: systemd (Ubuntu)
Status: Incomplete => Expired
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/168750
Sorry for slow response - I'm still trying to figure out the steps to reproduce
this reliable.
It does happen when I use my snap in the CI system (installing, testing,
removing).
It happens reliable with my CI system testing my snap (frr) when I do
run it against a commercial protocol compliance
is this leaks from snaps onto host system, generated by
mounting/unmounting of snaps? Does snapd insures to close/stop all
sessions that are started for each snap?
If normal snapd operations result in pam_logind creating sessions which
are never ended, and these sessions leak onto the host system,
Please provide steps to reproduce the issue.
** Changed in: snapd
Status: Invalid => Incomplete
** Changed in: systemd (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.laun
expanding on: "looking at the listing"
i meant to say, there are only very few related snap bits in there, many
are simply from the OS itself including apt updates and the like that
are completely unrelated to snaps.
--
You received this bug notification because you are a member of Ubuntu
Bugs,