Package: atop Version: 1.23-1 Severity: normal
Atop sometimes consumes huge amounts of memory, apparently triggered by tiger's check_system script and usually ending in an oom on my system (amd64 with 1GB ram) and since atop runs by default with nice -20, the oomkiller usually kills off a bunch of xterms before finally deciding to kill atop. I suspect that it was also causing occasional ooms when I had 2gigs in my system, but haven't verified it. I don't know yet what exactly is going on, but I think that tiger is creating large amounts of accounting information and atop is periodically trying to process all accounting information into some much larger in-memory representation at once. I've seen atop passing 800 megs in RSS when this happens, and trying to trigger it deliberately atop swelled to over 600 megs and then shrunk back to normal size. The time it hit 600, /tmp/atop.d/atop.acct was over 60megs. -- System Information: Debian Release: squeeze/sid APT prefers testing APT policy: (700, 'testing'), (500, 'stable') Architecture: amd64 (x86_64) Kernel: Linux 2.6.32-trunk-amd64 (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 atop depends on: ii libc6 2.10.2-6 Embedded GNU C Library: Shared lib ii libncurses5 5.7+20100313-1 shared libraries for terminal hand ii logrotate 3.7.8-4 Log rotation utility ii zlib1g 1:1.2.3.3.dfsg-15 compression library - runtime atop recommends no packages. atop suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
