[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#695866: marked as done (lintian: regression in memory usage or memory leak)

Your message dated Sat, 16 Feb 2013 13:47:32 +0000
with message-id <E1U6i72-00059T-LK@franck.debian.org>
and subject line Bug#695866: fixed in lintian 2.5.10.4
has caused the Debian Bug report #695866,
regarding lintian: regression in memory usage or memory leak
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 owner@bugs.debian.org
immediately.)


-- 
695866: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=695866
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: lintian
Version: 2.5.10.2
Severity: normal

Currently Lintian on lintian.d.o is doing a full run and top says:

 [...]  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 [...] 2567m 818m 1528 R   81 40.6 432:36.97 lintian

The run started on the 11th and I remember seeing it at 900ish VIRT/RES.
Yesterday, it was at 2.5 G VIRT (don't remember the RES).  Today, we are
still at 2.5 G VIRT and RES has been 800-1000 MB for the past 30 minutes.

We could be looking at a leak, because the VIRT is still growing a
bit.  Though, if so, only a subset of the packages triggers the leak.
I am more inclined to believe it is long-living objects that we no
longer have use, but still have a reference to.

L::Tags keeps a table of statistics for each file processed that is
not cleaned (afaict), so a slow grow is expected I guess.  However,
I have a feeling this is not the (only) cause of grow.

During the write up of this email the stats has changed to:

 [...]   VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 [...]  2699m 977m 1484 S    0 48.6 442:20.99 lintian 


If it is not a leak and just Perl not releasing memory back
(regardless of reason), I think we should look at splitting
full runs into smaller "short" lived processes.

~Niels

--- End Message ---
--- Begin Message --- 
Source: lintian
Source-Version: 2.5.10.4

We believe that the bug you reported is fixed in the latest version of
lintian, which is due to be installed in the Debian FTP archive.

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 695866@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.

Debian distribution maintenance software
pp.
Niels Thykier <niels@thykier.net> (supplier of updated lintian 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 ftpmaster@debian.org)


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Format: 1.8
Date: Sat, 16 Feb 2013 14:17:03 +0100
Source: lintian
Binary: lintian
Architecture: source all
Version: 2.5.10.4
Distribution: unstable
Urgency: low
Maintainer: Debian Lintian Maintainers <lintian-maint@debian.org>
Changed-By: Niels Thykier <niels@thykier.net>
Description: 
 lintian    - Debian package checker
Closes: 695866 696230 698602
Changes: 
 lintian (2.5.10.4) unstable; urgency=low
 .
   * checks/init.d:
     + [NT] Fix regression where Lintian would not properly match
       init.d passed to update-rc.d.  Thanks to Michael Meskes for
       reporting.  (Closes: #698602)
 .
   * lib/Lintian/Collect/Package.pm:
     + [NT] Ensure the "root" entry of indices do not contain itself.
       (Closes: #695866)
   * lib/Lintian/Util.pm:
     + [NT] Reject partially signed Deb822 files.  Most Deb822 files
       are not signed at all; but those that are should be completely
       covered by a signature.  (Closes: #696230)
     + [ADB] Fix a typo in the matching of expected delimiters for some
       signed messages; thanks Samuel Bronson.
Checksums-Sha1: 
 a541a224400bbc0aefe02c58632fdcf45898cea9 2564 lintian_2.5.10.4.dsc
 bc05a90de231dce5cfbc0c2fba1c3042408c7bdf 1099969 lintian_2.5.10.4.tar.gz
 7e68a82e21defc9cf2740560770b664feef8809a 708946 lintian_2.5.10.4_all.deb
Checksums-Sha256: 
 b5c0c59c7056e60f6acc8c33a0cdbce118f4ccea724169ec4fae278ba9e7ae63 2564 lintian_2.5.10.4.dsc
 d6b174b89efd1035821fa25121aebe46eb079d5cce025f1a5c68c1cb4647bdb2 1099969 lintian_2.5.10.4.tar.gz
 bdb1375de2b0857f5088964fe22cb7b1d6fba9418a5b3fef9af0d10b722fbb81 708946 lintian_2.5.10.4_all.deb
Files: 
 390bb8279734aa3a366e0836a8f4a631 2564 devel optional lintian_2.5.10.4.dsc
 1b92d5e6f1c9c3791cb8eea2269dd28f 1099969 devel optional lintian_2.5.10.4.tar.gz
 83c471d79fb0a6659d5a27e521d44cbd 708946 devel optional lintian_2.5.10.4_all.deb

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)

iQIcBAEBCAAGBQJRH4xQAAoJEAVLu599gGRCD4oP/2WWhDOOb3x0xCKLmwqBuyaE
fV9dgYNzJ8qdDD1X99TnjRD5TEVoXySNpHmc3g2PakRRt6Gs08rfwshkN8sRMGU9
mDgB/pT4FUgvdq7b882IdJv34AOEP/nxxpcV++SbLjXQKpbaJZnKVGaQNKN4Q0P4
4F4fLRwAlykmB8yPe2/gQZKOXRUk7SEpGrwnGg3wppwg3UUEeGinAg/GZDdkUBKg
+59XOTYi5du6cLwCf5Q00sgeBWvfzXFPZalC2PW9VTaj3Aajb2wd0yeMyZnuX73l
PJfxuQBlHNmm73RcAHsQ4VLSHzQQaqCfC0RnnGPxN2wPhVn5zNjI8gDL6/FeDsUP
xb4FFGqSSvwPMxkzoq0yYpSxPlied0dwl0halUiGtq/0M4n+MH3wwH+Xa4hAYZg9
e9QHllqYEOlZh29TTQ6HYAuBxJNVeKSs9zBS+Ikfq3CwGW13yy3vDFWsff/eIJ8T
8ZJdjaln+h+MhAxIuFokbdctbp4xDiIiDne1u6GQB5B8fyYDhugukxbbmpGFRIaE
EccuGCfFcV3ze3sHaPvfOz0bM4FIj98mM2AJKXKmX6Gq3/+/ijI8w5outuFUeKa/
Dr8BP5NjGmEtb9EkRWyX1CyWj1tsrFHMrhklwmqWoQ0aJ2WGYMU7t6nv88Mxt3Qa
HKQgqPGTipl6qOHsmaRt
=vVDe
-----END PGP SIGNATURE-----

--- End Message ---
Reply to: