Comment 4 for bug 225615

I should probably make it clearer that the screenshot was taken *after* all the downloads were completed!

But even if gvfsd-http would use that much memory only while downloading it would be a major bug! I mean come on, holding a multiple GB file completely in memory while downloading? There has to be a better way!

I'm lucky because I have 4GB of RAM, most people wouldn't be so lucky. Their systems would slow down to a crawl because of all the swapping.

I don't know how to invoke the gvfsd-http backend manually under valgrind. And the output would probably not be very useful without debug symbols anyway...
If you tell me specifically how to start gvfsd and how to stop it correctly (because if I just kill it the valgrind output would also not be very useful), I'd be happy to provide valgrind output.

But this issue should be really easy to reproduce: Just find something to download that's larger than 20 MB, then drag the link to your desktop and watch gvfsd-http eat your memory and stay that way even after the download is finished.