Yu Watanabe
Yu Watanabe
@poettering All preparatory commits have been merged. Now, only the main part. PTAL.
Even when two interfaces are enabled, is the expected result obtained by specifying `--interface=wl` in `resolvectl` ?
Could you provide debugging logs of resolved during the query?
It sounds the memleak is real. Reopening.
With v258-rc2, I cannot reproduce the issue. Tested with https://github.com/systemd/systemd/pull/38346/commits/beaa765977592bf6c6ef46360ba1a59ebc7203d8 but heaptrack does not find any leak.
Also with v257.7 and v257.3 I cannot reproduce the issue. heaptrack could not find any leak.
@fredlawl and @kroemeke Could you try to find memleak with [heaptrack](https://github.com/KDE/heaptrack) ? It is super simple, 1. start monitoring on a terminal ``` $ sudo heaptrack --pid 1 ``` 2....
Interestingly, still I cannot reproduce the issue even with ExecStartPre=, but I observed segfault in PID1: ``` [152345.210306] kernel: systemd[1]: segfault at 7ffeca193b2f ip 00007ffeca193b2f sp 00007ffeca193b20 error 15 likely...
@kroemeke Unfortunately, as already explained by Lennart in the above, it provides mostly no information, and does not help what causes the issue. Neither, it does not explain if it...
The latest failure: https://github.com/systemd/systemd/actions/runs/16465907474/job/46543116595?pr=38292