Package: arbtt Version: 0.10.1-1 Severity: normal I'm running arbtt-recover on a 140 mb capture.log, it's written out 75 mb of capture.log.recovered so far, and it's using 2.5 gb of memory.
I don't think it should need to keep the whole log read so far in memory, since it's written out to disk, should it? And if it did, there is probably a data structure that's not 18x larger than the data in the log. -- System Information: Debian Release: buster/sid APT prefers unstable-debug APT policy: (500, 'unstable-debug'), (500, 'unstable'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 4.19.0-4-amd64 (SMP w/4 CPU cores) Kernel taint flags: TAINT_USER, TAINT_WARN, TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE Locale: LANG=en_US.utf8, LC_CTYPE=en_US.utf8 (charmap=UTF-8), LANGUAGE=en_US.utf8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Init: systemd (via /run/systemd/system) LSM: AppArmor: enabled Versions of packages arbtt depends on: ii libatomic1 8.3.0-6 ii libc6 2.28-8 ii libffi6 3.2.1-9 ii libgmp10 2:6.1.2+dfsg-4 ii libpcre3 2:8.39-12 ii libx11-6 2:1.6.7-1 ii libxext6 2:1.3.3-1+b2 ii libxinerama1 2:1.1.4-2 ii libxrandr2 2:1.5.1-1 ii libxss1 1:1.2.3-1 arbtt recommends no packages. arbtt suggests no packages. -- no debconf information -- see shy jo
signature.asc
Description: PGP signature
