Package: tinyproxy Version: 1.8.1-3 Severity: important
Hi - It appears that Tinyproxy 1.8.1 has a memory leak. Regardless of usage, if Tinyproxy is left running for a couple of days, the resident size of the parent process + children increase substantially. This happens on both amd64 and i386 systems with a more-or-less default configuration file (only "Allow" directives were modified). For example, here's ps output showing Tinyproxy after running for 4-5 days: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nobody 9508 0.0 1.9 11524 9920 ? S< Apr23 0:02 /usr/sbin/tinyproxy nobody 9509 0.0 3.4 19140 17604 ? S< Apr23 0:05 \_ /usr/sbin/tinyproxy nobody 9510 0.0 3.4 19140 17540 ? S< Apr23 0:05 \_ /usr/sbin/tinyproxy nobody 9511 0.0 3.4 19140 17576 ? S< Apr23 0:04 \_ /usr/sbin/tinyproxy nobody 9512 0.0 3.4 19140 17576 ? S< Apr23 0:04 \_ /usr/sbin/tinyproxy nobody 9514 0.0 3.4 19140 17536 ? S< Apr23 0:04 \_ /usr/sbin/tinyproxy nobody 9515 0.0 3.4 19140 17544 ? S< Apr23 0:04 \_ /usr/sbin/tinyproxy nobody 9516 0.0 3.4 19140 17516 ? S< Apr23 0:05 \_ /usr/sbin/tinyproxy nobody 9518 0.0 3.4 19140 17564 ? S< Apr23 0:04 \_ /usr/sbin/tinyproxy nobody 15789 0.0 2.3 13452 11980 ? S< Apr26 0:04 \_ /usr/sbin/tinyproxy nobody 15798 0.0 2.3 13452 12024 ? S< Apr26 0:04 \_ /usr/sbin/tinyproxy nobody 15811 0.0 2.3 13452 12040 ? S< Apr26 0:04 \_ /usr/sbin/tinyproxy nobody 15820 0.0 2.3 13452 12024 ? S< Apr26 0:04 \_ /usr/sbin/tinyproxy nobody 2745 0.0 2.3 13452 12020 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 2758 0.0 2.3 13452 12068 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 2767 0.0 2.3 13452 12032 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 3086 0.0 2.3 13452 12040 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 5966 0.0 2.3 13452 12012 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 6540 0.0 2.3 13452 12060 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 6549 0.0 2.3 13452 12000 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 6571 0.0 2.3 13452 12024 ? S< Apr26 0:03 \_ /usr/sbin/tinyproxy nobody 22222 0.0 1.9 11552 10096 ? S< 08:26 0:00 \_ /usr/sbin/tinyproxy However, upon restart, the memory footprint starts out much smaller: USER PID %CPU %MEM VSZ RSS TTY STAT START TIME COMMAND nobody 25982 0.0 0.4 3932 2416 ? S< 13:29 0:00 /usr/sbin/tinyproxy nobody 25983 0.0 0.5 3960 2684 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25984 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25985 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25986 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25987 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25988 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25989 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25990 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25991 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy nobody 25992 0.0 0.4 3932 2100 ? S< 13:29 0:00 \_ /usr/sbin/tinyproxy This bug did not exist in 1.6.3, it was apparently introduced between 1.6.3 and 1.8.1. All systems I've tested this on are dual-stack IPv4/IPv6, if this matters. Again, the Tinyproxy processes do not grow due to traffic. I can start up Tinyproxy, have it handle no proxy traffic, and the processes will still grow in size over time. Please let me know if I can provide any additional information. This is fairly easy to recreate, here. - Mark -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (500, 'testing') Architecture: i386 (i686) Kernel: Linux 2.6.32-trunk-686 (SMP w/2 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages tinyproxy depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii logrotate 3.7.8-5 Log rotation utility tinyproxy recommends no packages. tinyproxy suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
