This libpcre2 library seems to be the only one, which is not used all over the place. The library itself may not even be buggy, it may just return something, which the new versions of the caller can't handle, or it may be unhappy with something the new callers send.
Still: if you can tie this memory/cpu leak to the interaction between application and that library, it should be much easier to identify the offending commit in nginx and all the other affected programs. I just saw, that the version 8 of libpcre2 seems to be quite a bit behind the current version: https://github.com/PCRE2Project/pcre2/releases Is this intentional? On Sun, 2023-09-24 at 12:59 +0200, Tobias Fiebig wrote: > They do, but nothing special. The common set between nginx and mysqld > is: > > /usr/local/lib/libpcre2-8.so.0.6 > /usr/lib/libssl.so.53.2 > /usr/lib/libcrypto.so.50.2 > /usr/lib/libz.so.7.0 > /usr/lib/libc.so.97.0 > /usr/libexec/ld.so > > However, an affected nginx (1.24.0) does not differ from an > unaffected > nginx (1.23.1). > > I somewhat hope that my testing through nginx commits will yield what > calls are actually involved, and may allow me to see whether mysql is > pushed into similar codepaths on affected systems (and not on > unaffected ones), likely giving a better hint as to where the issue > is. > > With best regards, > Tobias > > On Sun, 2023-09-24 at 12:53 +0200, Rudolf Leitgeb wrote: > > Do the affected programs use the same libraries? > > > > On Sun, 2023-09-24 at 09:32 +0200, Tobias Fiebig wrote: > > > After upgrading to 7.3 and nginx-1.24.0, i started to see heavy > > > memory > > > leakage over time. I initially attributed this to nginx, and > > > solved > > > the > > > issue by ignoring it/throwing a bit more memory at the box for > > > some > > > time. However, I started debugging it now and could trace it to > > > some > > > commit between nginx 1.23.3 and 1.23.4; Currently, I am going > > > through > > > all commits to see with which version it first appears. > > > > > > However, clicking around this morning, i noticed that my primary > > > NS > > > shows a similar memory leakage for mysql/mariadb (runs powerdns > > > with > > > a > > > mysql backend, both from packages) since the upgrade to 7.3 in > > > May > > > as > > > well. One further host seems to show a significantly higher use > > > of > > > inactive memory since 7.3. I found one more host with mariadb > > > that > > > now > > > shows a higher utilization of inactive memory (gitea+maria); > > > However, > > > other maria+X instances on 7.3 run fine. > > >
