Your message dated Wed, 02 Jun 2010 13:10:35 +0000
with message-id <[email protected]>
and subject line Bug#579427: fixed in tinyproxy 1.8.1-5
has caused the Debian Bug report #579427,
regarding tinyproxy: Tinyproxy leaks memory over time
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
579427: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=579427
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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
--- End Message ---
--- Begin Message ---
Source: tinyproxy
Source-Version: 1.8.1-5
We believe that the bug you reported is fixed in the latest version of
tinyproxy, which is due to be installed in the Debian FTP archive:
tinyproxy_1.8.1-5.debian.tar.bz2
to main/t/tinyproxy/tinyproxy_1.8.1-5.debian.tar.bz2
tinyproxy_1.8.1-5.dsc
to main/t/tinyproxy/tinyproxy_1.8.1-5.dsc
tinyproxy_1.8.1-5_amd64.deb
to main/t/tinyproxy/tinyproxy_1.8.1-5_amd64.deb
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Jordi Mallach <[email protected]> (supplier of updated tinyproxy package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Format: 1.8
Date: Wed, 02 Jun 2010 09:43:50 +0200
Source: tinyproxy
Binary: tinyproxy
Architecture: source amd64
Version: 1.8.1-5
Distribution: unstable
Urgency: medium
Maintainer: Ed Boraas <[email protected]>
Changed-By: Jordi Mallach <[email protected]>
Description:
tinyproxy - A lightweight, non-caching, optionally anonymizing http proxy
Closes: 579427
Changes:
tinyproxy (1.8.1-5) unstable; urgency=medium
.
* Add sighup_memleak.patch, by John van der Kamp, to fix a memleak
when reloading tinyproxy, which happens daily via logrotate
(closes: #579427).
* Adjust testsuite_user_var.patch to use output of "id -un" instead of
"whoami".
Checksums-Sha1:
10565cc0101f6a44819e6d8dd72cfe9f136b1038 1263 tinyproxy_1.8.1-5.dsc
fe572e25a7283ed0dec00f8c97fe3b4cc14b7f46 13775 tinyproxy_1.8.1-5.debian.tar.bz2
5dc084bbf2bba1d7ac612a353fff4066a1213904 85726 tinyproxy_1.8.1-5_amd64.deb
Checksums-Sha256:
3415318c274dcd29c20ef6935e8ea0f9a8d9aa43566a922728da51f7bc479f85 1263
tinyproxy_1.8.1-5.dsc
bc880d1bd1e51be0f3a657815bd83443bc7a4dde6f81b6ed7fc7bd9eb4e912d8 13775
tinyproxy_1.8.1-5.debian.tar.bz2
72a078bd51de89f9dae56d0eaea570a3f54fbc2c33b629c0af254a453434bf07 85726
tinyproxy_1.8.1-5_amd64.deb
Files:
d29a7cfa599267fbaae0d57149c8961f 1263 web optional tinyproxy_1.8.1-5.dsc
ef6070d88f7d794847f71a17a4574240 13775 web optional
tinyproxy_1.8.1-5.debian.tar.bz2
b7308b8370711a69baca17f7f4a363c8 85726 web optional tinyproxy_1.8.1-5_amd64.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (GNU/Linux)
iEYEARECAAYFAkwGT30ACgkQJYSUupF6Il4B3gCfQEgtJLt+qL3DotEYO9jP099s
ua0AoIG3Hw3xlwv7qvMVmjtg5mS77CfP
=mjhM
-----END PGP SIGNATURE-----
--- End Message ---
