On Wed, Aug 30, 2006 at 12:50:10AM +0200, Tomas Pospisek wrote: > >Running filelight over my 100Gb home directory (600k inodes, ~10 > >million files) resulted in it allocating 400Mb of memory, of which > >200Mb was actually used. > > Could you double check this? To me it looks like filelight is doing better > these days. Scanning my 20G partition with 500k files: > > PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND > 17044 tpo 16 0 70176 48m 13m S 0.0 6.4 0:35.73 filelight
I now have 800k files and a roughly equal number of inodes (no huge hardlink forest these days), using 90Mb/70Mb, which is more reasonable (still more than xdiskusage, but probably attributable to Qt waste rather than a bug). Unless it had something to do with the hardlinks, I expect this changelog entry is the relevant one: 1.0-beta3 Found big memory leak thanks to valgrind! -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]