severity 386457 important tags 386457 unreproducible moreinfo thanks On Thu, Sep 07, 2006 at 02:46:47PM -0400, [EMAIL PROTECTED] wrote:
> updatedb during it's run consumes almost all of the system's available > memory (as reported by top), and fails to release it when the run is > complete. The memory consumption at the end of the run appears to be > about 1/3 kernel and 2/3 userspace for ALL of the memory in the > system, however adding up the memory used by the running processes > after the updatedb run completes does not come anywhere near the total > memory usage reported by top. This bug appears during findutils daily > run and at any time that updatedb is invoked independently. > I have managed to reproduce this behaviour, on demand, on two machines > (both running Debian/unstable). One is an AMD64 with 1GB of RAM, and > the other is an i386 with 512MB of RAM. Both machines show the same > relative memory consumption patters. It should be noted that nothing > is swapped out on either machine. Both machines are running kernel > 2.6.17. A process doesn't use any memory after it's done; the memory is freed by the kernel. If not, that would be a kernel bug. But how have you determined that the memory is "in use"? It sounds to me like you're misidentifying disk cache as "used" memory. > The severity is set to grave because this bug makes the entire system > unusable until it is rebooted. What is unusable about it? -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. [EMAIL PROTECTED] http://www.debian.org/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
