Received: (at submit) by bugs.debian.org; 27 Jun 2001 01:59:20 +0000 From Marcus.Brinkmann@ruhr-uni-bochum.de Tue Jun 26 20:59:20 2001 Return-path: Received: from (ulysses.g10code.de) [::ffff:212.23.136.22] by master.debian.org with esmtp (Exim 3.12 1 (Debian)) id 15F4bv-00041Z-00; Tue, 26 Jun 2001 20:59:20 -0500 Received: from marcus by ulysses.g10code.de with local (Exim 3.16 #3 (Debian)) id 15F4bg-0001lN-00 for ; Wed, 27 Jun 2001 03:59:04 +0200 Date: Wed, 27 Jun 2001 03:59:03 +0200 To: submit@bugs.debian.org Subject: proc leaks memory with the bootstrap filesystem entry Message-ID: <20010627035903.A3552@212.23.136.22> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2i From: Marcus Brinkmann Delivered-To: submit@bugs.debian.org Package: hurd Version: current Hi, this is really a nice obscure bug. Calling proc_getprocinfo on PID 4 (root filesystem server) causes proc to leak a couple of kilobytes (pages?) each time. This can easily be reproduced by ps -F hurd 0 ps -F hurd 4 ps -F hurd 0 etc. Do this right after booting, so RSS for proc is still under 1 MB (this makes it easier to see). To prove that PID 4 is the only process with this problem, the below program iterates over all pids. If you specify any command line arguments, it will skip PID 4. In this case, no memory is leaked. This is most certainly a bootstrap issue. Interestingly, the same behaviour is exposed in a sub hurd (for the sub hurds root filesystem and the sub hurds proc server). I have no concrete idea yet to what the actual bug is. Any hints, as always, appreciated. BTW, fork() makes proc leak memory as well. Reproduce with "forks 1000 10000". This seems to be an unrelated bug, which I plan to investigate after this one is fixed. Thanks, Marcus