I cannot reproduce it on either coreutils upstream (currently at version 8.5.118-abd04) or on Maverick coreutils (version 8.5-1ubuntu3). Both report: ==4838== LEAK SUMMARY: ==4838== definitely lost: 0 bytes in 0 blocks ==4838== indirectly lost: 0 bytes in 0 blocks ==4838== possibly lost: 0 bytes in 0 blocks ==4838== still reachable: 34,801 bytes in 91 blocks ==4838== suppressed: 0 bytes in 0 blocks
On the other hand, if you can observer free memory going down on a loop of 'ls', then this is not a bug on coreutils: the lost/unreachable memory segments would have been freed when 'ls' ended; if these segments are not being freed, then the problem is outside coreutils. I do not have a 10.04 system available to test. Could you please attach the valgrind log here? -- ls has memory leak https://bugs.launchpad.net/bugs/606803 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
