> On 2012-12-13 10:55, Niels Thykier wrote: >> [...] > > The bad news first; Lintian 2.5.11 was unable to finish the full > run. Around gnome-scan, Lintian started spewing errors - first a > fork failed and then a couple of: """[...] cannot open X: Cannot > allocate memory at ... """ > > After that, it just said "collect info X of ... failed" a couple > of times for each of the remaining packages. The VIRT memory usage > had grown over 3GB, so I now strongly suspect that 2.5.11 > introduces a memory leak. > > [...] > > ~Niels > >
top tells me that Lintian starts its memory usage at about 450MB/300MB and ends at about 620MB/450MB[1]. During this interval, Lintian processed about 512 groups[2]. Assuming the entire change is a leak, Lintian is leaking (avg) 0.33 MB per "group". That said, the leaks do not seem be "per package". Instead they appear to come in "spikes". I noticed spikes near ace, libtao-orbsvcs, libtao-doc and acl2, which may (or may not) be triggering the leak. ~Niels [1] [...] VIRT RES SHR S %CPU %MEM TIME+ COMMAND [...] 450m 306m 2164 S 0 15.2 0:28.37 lintian [...] 621m 449m 3356 S 0 22.3 33:22.56 lintian [2] So about 512 source packages and (estimated) 1000 binaries. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
