I think it's the same as: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=921146 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923711 But it doesn't depend on using -mem option (I never use it), it is a general memory leak that, in my case, ends up with OOMKiller needing to kill it I am trying to find the offending patch causing this regression over _p7
Fixed URLs: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=923711 https://github.com/plougher/squashfs-tools/issues/60
Dropping 0016-remove-frag_deflator_thread.patch and 0017-add-zstd-support.patch stops the memory leak
Weird. Is it defaulting to zstd?
The real culprit is only 0016-remove-frag_deflator_thread.patch (just checked now) I experience this with XZ compression
The bug has been referenced in the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=403e623c705521b9e6ae590f38a6d9599b4a23aa commit 403e623c705521b9e6ae590f38a6d9599b4a23aa Author: Jeroen Roovers <jer@gentoo.org> AuthorDate: 2019-03-18 16:52:21 +0000 Commit: Jeroen Roovers <jer@gentoo.org> CommitDate: 2019-03-18 16:52:45 +0000 sys-fs/squashfs-tools: Drop 0016-remove-frag_deflator_thread.patch Package-Manager: Portage-2.3.62, Repoman-2.3.12 Bug: https://bugs.gentoo.org/680844 Signed-off-by: Jeroen Roovers <jer@gentoo.org> .../squashfs-tools-4.3_p11-r1.ebuild | 85 ++++++++++++++++++++++ 1 file changed, 85 insertions(+)
0016-remove-frag_deflator_thread.patch purportedly fixing something to do with LZO. Not entirely sure. Could you try -r1?
commit 62080301b42cc144c9e66e67bcbcc7785fec6322 (HEAD -> master, origin/master, origin/HEAD) Author: Jeroen Roovers <jer@gentoo.org> Date: Wed Apr 10 13:40:20 2019 +0200 sys-fs/squashfs-tools: Version 4.3_p12 Package-Manager: Portage-2.3.62, Repoman-2.3.12 Signed-off-by: Jeroen Roovers <jer@gentoo.org>
Hm, maybe it isn't fixed yet? I just read the comments on the upstream tracker and it looks like Debian has patched the patch.
it seems it works ok now :)
