Re: [fuse-devel] Memory leaking when writing large files?

[Stef B. <st...@gm...>]

Hi,

I've already found an issue. The function open_ino creates a temp new
object pathinfo, but does not free it.

Stef

2010/7/18 Stef Bon <st...@gm...>:
> Hello,
>
> I've found out that when moving a file from one place to the other,
> the memory my fs is using is growing and growing..
>
> My fs is a lowlevel fs, using the at commands like openat, fgetxattr and so on.
>

>
> The write call only provides one logmessage (write), but the getxattr
> produces more.
> It tries to open the inode, and that causes the various path messages.
> (there is a conversion from inode->absolute path->path relative to an
> existing fd)
>
> By the way, the file is already open for the write call
> (exclusive/rdwr) with fd 8, and getxattr opens the file again (the
> open_ino call) readonly, fd 9.
> This is possible, but double.
>
> Now how do I find there is a memory leak??
> First, is necessary to free the buffer in the write call at the end of
> the call? I do not have that at this moment.
>
> If not, I've read something about valgrind. Is this the way to tackle this?
>
> Thanks in advance,
>
> Stef
>
> PS I'm visiting the open source for government conference in Den Hage
> at July 26:
>
> http://www.guadec.org/index.php/guadec/2010/schedConf/opendesktopday
>
> and thinking about going to the openSuse conference at 20-23 oktober
> in Nurnberg, Germany.
> I thinking about giving a presentation about my fs:
>
> http://en.opensuse.org/Conference_2010/Call_For_Papers
>