Package: reportbug Version: 3.33 Severity: normal 32357 joey 15 0 38036 32m 2720 S 0.0 6.6 0:04.49 reportbug
Could reportbug please not eat half my memory when I ask it to report a bug
on a udeb such as s390-dasd?
While this memory usage growth is going on, I see:
32563 pts/12 S+ 0:00 | \_ /usr/bin/python -S
/usr/bin/reportbug -b --no-check-available -x -M --mode=expert s390-dasd
32605 pts/12 S+ 0:00 | \_ sh -c { apt-cache dumpavail
2>/dev/null; } 2>&1
32608 pts/12 R+ 0:00 | \_ apt-cache dumpavail
[EMAIL PROTECTED]:~>apt-cache dumpavail | wc -c
22349240
It's reading all that into memory. It's especially bad since I have testing
and unstable both in sources.list.
avail = commands.getoutput('apt-cache dumpavail 2>/dev/null')
There *are* better ways to do this.
-- Package-specific info:
** Environment settings:
EDITOR="vim"
VISUAL="vim"
DEBEMAIL="[EMAIL PROTECTED]"
-- System Information:
Debian Release: 4.0
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing'), (1, 'experimental')
Architecture: i386 (i686)
Shell: /bin/sh linked to /bin/bash
Kernel: Linux 2.6.18-4-686
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Versions of packages reportbug depends on:
ii python 2.4.4-2 An interactive high-level object-o
ii python-central 0.5.12 register and build utility for Pyt
reportbug recommends no packages.
-- no debconf information
--
see shy jo
signature.asc
Description: Digital signature
