| 2021-07-08 13:48:06 |
Sergey Borodavkin |
bug |
|
|
added bug |
| 2021-07-08 13:48:06 |
Sergey Borodavkin |
attachment added |
|
pid1 strace focal https://bugs.launchpad.net/bugs/1935051/+attachment/5509910/+files/pid1_strace_focal |
|
| 2021-07-08 13:48:38 |
Sergey Borodavkin |
attachment added |
|
pmap_pid1_focal https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1935051/+attachment/5509911/+files/pmap_pid1_focal |
|
| 2021-07-08 13:50:39 |
Sergey Borodavkin |
systemd (Ubuntu): status |
New |
Incomplete |
|
| 2021-07-08 13:50:51 |
Sergey Borodavkin |
systemd (Ubuntu): status |
Incomplete |
New |
|
| 2021-07-08 13:54:34 |
Sergey Borodavkin |
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.
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 |
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 |
|
| 2021-07-08 13:55:09 |
Sergey Borodavkin |
tags |
systemd |
pid1 systemd |
|
| 2021-07-08 17:33:16 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2021-08-20 12:04:38 |
Dan Streetman |
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 |
[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 |
|
| 2021-08-20 12:04:43 |
Dan Streetman |
nominated for series |
|
Ubuntu Focal |
|
| 2021-08-20 12:04:43 |
Dan Streetman |
bug task added |
|
systemd (Ubuntu Focal) |
|
| 2021-08-20 12:04:49 |
Dan Streetman |
systemd (Ubuntu): status |
New |
Fix Released |
|
| 2021-08-20 12:04:51 |
Dan Streetman |
systemd (Ubuntu Focal): status |
New |
In Progress |
|
| 2021-08-20 12:04:53 |
Dan Streetman |
systemd (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2021-08-20 12:04:56 |
Dan Streetman |
systemd (Ubuntu Focal): assignee |
|
Dan Streetman (ddstreet) |
|
| 2021-09-02 12:48:35 |
Łukasz Zemczak |
systemd (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2021-09-02 12:48:36 |
Łukasz Zemczak |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2021-09-02 12:48:38 |
Łukasz Zemczak |
bug |
|
|
added subscriber SRU Verification |
| 2021-09-02 12:48:40 |
Łukasz Zemczak |
tags |
pid1 systemd |
pid1 systemd verification-needed verification-needed-focal |
|
| 2021-09-06 08:51:55 |
Sergey Borodavkin |
tags |
pid1 systemd verification-needed verification-needed-focal |
pid1 systemd verification-done-focal verification-needed |
|
| 2021-09-06 13:51:11 |
Dan Streetman |
tags |
pid1 systemd verification-done-focal verification-needed |
pid1 systemd verification-done verification-done-focal |
|
| 2021-09-07 21:07:12 |
Brian Murray |
tags |
pid1 systemd verification-done verification-done-focal |
pid1 systemd verification-needed verification-needed-focal |
|
| 2021-09-08 11:03:47 |
Sergey Borodavkin |
tags |
pid1 systemd verification-needed verification-needed-focal |
pid1 systemd verification-done verification-done-focal |
|
| 2021-09-15 03:17:01 |
Chris Halse Rogers |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2021-09-15 03:24:04 |
Launchpad Janitor |
systemd (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
