[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[bug #33207] updatedb (findutils-locate) has a memory leak on large nfs

From: James Youngman
Subject: [bug #33207] updatedb (findutils-locate) has a memory leak on large nfs mounts, the index is not complete
Date: Sat, 14 May 2011 23:37:36 +0000
User-agent: Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/534.10 (KHTML, like Gecko) Chrome/8.0.552.224 Safari/534.10

Follow-up Comment #3, bug #33207 (project findutils):

Two other things that would be helpful in diagnosing this:

1. Check which directories the find process has open at two points in its
execution, say 5 minutes apart.   You can do this with "lsof" or by examining
/proc.   I'm mainly interested if all this memory consumption is a result of
taking a long time to process one specific directory, or whether we have some
kind of memory leak in which memory used for processing a directory is never
freed even after we leave it.

2. Figure out if the old find implementation suffers from the same problem
(they only have some of the code in common).   You can figure this out by
specifying the option "--without-fts" to configure (this causes the non-fts
based binary to be called "find" and the fts-based binary to be called


Reply to this item at:


  Message sent via/by Savannah

reply via email to

[Prev in Thread] Current Thread [Next in Thread]