Hi, On 2023-07-03 22:15, Aurelien Jarno wrote: > It's not clear to me either what's the issue. So far I have just found > that the virtual memory allocation of plasmashell is ~11GB with glibc > 2.37 vs ~2GB with glibc 2.36. In both cases the resident memory is > around 350MB. This higher virtual memory allocation seems to cause the > clone syscall to fail with -ENOMEM. > > > However, now the problem seems to have solved. > > Yes, it's great that you have found a workaround. Given that, I don't > think it warrants blocking the migration of glibc 2.37 to testing, but > I'll continue investigating to better understand if it could have other > side effects.
The issue is due to this upstream commit: https://sourceware.org/git/?p=glibc.git;a=commitdiff;h=f4f2ca1509288f6f780af50659693a89949e7e46 Other possible workarounds are: - defining the GLIBC_TUNABLES environment variable to "glibc.malloc.trim_threshold=128" - changing the kernelvm.overcommit_memory parameter to 1 with "sysctl vm.overcommit_memory=1" Regards Aurelien -- Aurelien Jarno GPG: 4096R/1DDD8C9B aurel...@aurel32.net http://aurel32.net
