This bug was fixed in the package systemd - 245.4-4ubuntu3.13
---------------
systemd (245.4-4ubuntu3.13) focal; urgency=medium
* d/p/dell-clamshell-accel-location-base-with-sku.patch:
Revert incorrect patch (LP: #1942899)
systemd (245.4-4ubuntu3.12) focal; urgency=medium
[ Yao Wei ]
* d/p/dell-clamshell-accel-location-base.patch:
Add ACCEL_LOCATION=base property for Dell clamshell models (LP: #1938259)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=5c1be33900edee94da0dc9a4ade8edcd079b4c85
[ Lukas Märdian ]
* Add d/p/lp1934221-resolved-disable-event-sources-before-unreffing-them.patch
- Fix segfault in systemd-resolve (LP: #1934221)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=6c401900c70962052f56c7108fdc02fe7f84c9bf
[ Simon Chopin ]
* d/p/lp1914740-network-enable-DHCP-broadcast-flag-if-required-by-in.patch:
- Apply upstream patch to fix Hipersocket DHCP mode (LP: #1914740)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=326ae43b7966d9e7c5f7124027185a79a07fa276
[ Dan Streetman ]
* d/p/lp1934981-correct-suspend-then-sleep-string.patch:
Fix sleep verb used by logind during suspend-then-hibernate
(LP: #1934981)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=997f3a7da3d5db22e3c63626c3f7dc3dff0830b0
* d/p/lp1937238-util-return-the-correct-correct-wd-from-inotify-help.patch:
Fix watch for time sync (LP: #1937238)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=dbabff8a03eb232c19174eff1335cd7cb7d7860c
* d/extra/dhclient-enter-resolved-hook:
Reset start limit counter for systemd-resolved in dhclient hook
(LP: #1939255)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=9d3a91a0b70a4b2bcc166f366cd0a880fd494812
* d/p/lp1935051-shared-unit-file-make-sure-the-old-hashmaps-and-sets.patch:
Fix memory leak in path cache (LP: #1935051)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=12d6bdeb35f309158fe8d4242c6dd9be4d067604
*
d/p/lp1934147/0001-cgroup-do-catchup-for-unit-cgroup-inotify-watch-file.patch,
d/p/lp1934147/0002-core-Make-sure-cgroup_oom_queue-is-flushed-on-manage.patch:
Catchup cgroup inotify watch after reexec/reload (LP: #1934147)
https://git.launchpad.net/~ubuntu-core-dev/ubuntu/+source/systemd/commit/?id=63eabc88b8e0005eb40b15b543538ce35377bdbd
-- Dan Streetman <ddstr...@canonical.com> Tue, 07 Sep 2021 14:37:22
-0400
** Changed in: systemd (Ubuntu Focal)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Touch seeded packages, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1935051
Title:
systemd pid 1 memory leak
Status in systemd package in Ubuntu:
Fix Released
Status in systemd source package in Focal:
Fix Released
Bug description:
[impact]
pid1 leaks memory when rebuilding unit path cache
[test case]
see original description.
also, the patch contains an example of how to reproduce:
$ for i in {1..300}; do cp ~/.config/systemd/user/test0001.service
~/.config/systemd/user/test$(printf %04d $i).service; systemctl --user
start test$(printf %04d $i).service;done
[regression]
any problems would occur when rebuilding the path cache, possibly
resulting in memory leaks or pid1 crashes.
[scope]
this is needed only in f
fixed upstream by 3fb2326f3ed87aa0b26078d307ebfb299e36286d which is
included in v246, so fixed in h and later
the code in b is very different and doesn't appear to have the leak,
per original report
[original description]
Hi everybody.
We've meet a memory leak of pid1 process on the focal release.
When we launch chef-client, several systemd .service and .timers are checked
for state.
Every time of this run pid1 increase VSZ/RSS on ~ 232 Kb, this don't happen
on xenial and bionic releases.
I straced pid1 when that leak happen and found brk call.
On pmap view of pid 1 it's anon memory grow on the same address and all
marked as dirty.
All that leak memory can be freed by calling systemctl daemon-reexec.
Searching in systemd github repo i found this commit
https://github.com/systemd/systemd/commit/3fb2326f3ed87aa0b26078d307ebfb299e36286d
- it may be related to this leak.
------------------------------------------------------------------------
Environment:
Distributor ID: Ubuntu
Description: Ubuntu 20.04.2 LTS
Release: 20.04
Codename: focal
Uname: 5.4.0-77-generic #83-Ubuntu SMP Sat May 8 02:35:39 UTC 2021
x86_64
Package:
systemd:
Installed: 245.4-4ubuntu3.7
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+subscriptions
--
Mailing list: https://launchpad.net/~touch-packages
Post to : touch-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~touch-packages
More help : https://help.launchpad.net/ListHelp
