Ok Sebastien,
I suggested closing it some time ago, as I couldn't reproduce the
problem.
Many thanks to all who invested their time in this issue!
Regards,
Rob Wiers
> closing the bug it should be fixed in jaunty, you can open a new bug if
> you get some other issues in jaunty though
>
> ** Cha
closing the bug it should be fixed in jaunty, you can open a new bug if
you get some other issues in jaunty though
** Changed in: gvfs (Ubuntu)
Status: Incomplete => Fix Released
--
gvfsd allocates huge amounts of memory while playing audio files
https://bugs.launchpad.net/bugs/316093
You
After trying for nearly two weeks, I have to face up to the fact that I'm not
able to reproduce the bug anymore.
I'm not sure if this is due to patches and / or product updates, but I have
been running my music program more or less constantly and I haven't had virtual
memory rising on me as I ha
I'm having problems getting the replaced gvfsd to start. I've created a
wrapper script, similar to the one described in the pages of the other
bug. When I try to start it, it works, but doesn't come back in the
System Monitor (process is not listed there, even though it exists; I
can find it with p
the bug you listed there is specific to the webdav backend and has been
fixed in jaunty, gvfsd is usually stable, some backends are still buggy
and need work though
--
gvfsd allocates huge amounts of memory while playing audio files
https://bugs.launchpad.net/bugs/316093
You received this bug not
Searching for a way to replace the gvfsd I found the following bug (225615),
which gave me a bit of a deja-vu:
https://bugs.launchpad.net/bugs/225615. Am I mistaken or is gvfs very leaky?
Btw. I ___will___ try to produce a valgrind logfile, but I'm kind of
baffled by the behaviour of this relativ
Thanks... (Didn't think of that... ;-(
> the usual way to get logs for those is to rename gvfsd to gvfds.bin and
> create a gvfsd which calls valgrind on gvfsd.bin
>
--
gvfsd allocates huge amounts of memory while playing audio files
https://bugs.launchpad.net/bugs/316093
You received this bug n
the usual way to get logs for those is to rename gvfsd to gvfds.bin and
create a gvfsd which calls valgrind on gvfsd.bin
--
gvfsd allocates huge amounts of memory while playing audio files
https://bugs.launchpad.net/bugs/316093
You received this bug notification because you are a member of Ubuntu
I have used System Monitor to kill the gvfsd process and that has
released the consumed swap, confirming my suspicions that gvfsd was
responsible for consuming the memory. Since gvfsd automatically gets
restarted, that kind of works for me, but I hope you agree it's not a
very good solution.
--
g
Hello Sebastien,
Thank you for picking up my bug report.
I understand your request, and have installed valgrind on my system.
However, since the program I suspect of leaking memory is gvfsd (I have
acutally managed to reclaim the memory by killing it; it restarts
automatically, and my swap is rele
Thank you for picking up my bug report.
I understand your request, and have installed valgrind on my system.
However, since the program I suspect of leaking memory is gvfsd (I have
acutally managed to reclaim the memory by killing it; it restarts
automatically, and my swap is released. I will put
Thank you for taking the time to report this bug and helping to make
Ubuntu better. Please try to obtain a valgrind log following the
instructions at https://wiki.ubuntu.com/Valgrind and attach the file to
the bug report. This will greatly help us in tracking down your problem.
** Changed in: gvfs
** Changed in: gvfs (Ubuntu)
Sourcepackagename: None => gvfs
--
gvfsd allocates huge amounts of memory while playing audio files
https://bugs.launchpad.net/bugs/316093
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gvfs in ubuntu.
--
d
13 matches
Mail list logo
