|
From: Jan K. <rcp...@ja...> - 2003-12-23 03:57:10
|
Hi, I have suspection libntfs is leaking memory. During NTFS disks scanning by captive-install-acquire of Captive NTFS through GnomeVFS and ntfsprogs-gnomevfs its leaking a lot, short scanning produces http://dmalloc.com output: top 10 allocations: total-size count in-use-size count source 75055104 18324 0 0 runlist.c:759 74174464 18109 74174464 18109 dir.c:238 29713408 29017 602112 588 mft.c:214 3069184 95912 0 0 attrib.c:1907 1468928 22952 52160 815 attrib.c:335 1160720 29018 23520 588 inode.c:44 Out of http://www.jankratochvil.net/project/captive/dist/captive-1.1.4.tar.gz it can be produced by (rm -f /tmp/dlog;eval `dmalloc -b runtime -l /tmp/dlog`;./captive-install-acquire --text -v --scan-path=file:///dev/hdc1#libntfs: ) or better (rm -f /tmp/dlog;eval `dmalloc -b runtime -l /tmp/dlog`;./captive-install-acquire --text -v ) and specify custom scanning path 'file:///dev/hdc1#libntfs:' by hand to be able to abort it soon by ENTER on the keyboard ('--scan-path' is abortable just by CTRL-C which prevents output of the dmalloc '/tmp/dlog' report). I did not yet investigate it much - are you aware of this leakage? I do not ntfs_umount() it but I hope I correctly ntfs_attr_close() and ntfs_inode_close() everything. Regards, Lace |
