correct, it will spike but this is due to the copying of the ff db
file. But after indexing, the memory goes back down, no?
On Sat, Sep 5, 2009 at 4:33 AM, Bernhard<email address hidden> wrote:
> Yes, it works much better. I might get re-indexing spikes of 0.5 MB with
> ff-mem-fix, but much better than the 10 MB spikes in current trunk.
>
> --
> [bzr] Firefox plugin eats a lot of memory
> https://bugs.launchpad.net/bugs/381064
> You received this bug notification because you are a bug assignee.
>
> Status in GNOME Do Plugins Project: In Progress
>
> Bug description:
> Since rev 1195 I feel like docky leaks a lot more memory. It goes up to 300MB if I wait 2 hours. I will attach a debug of events during which the memory usage went from 40MB to 130MB.
>
> EDIT: after further testing, it seems like the firefox plugin (bzr of May 27) is the problem.
>
correct, it will spike but this is due to the copying of the ff db
file. But after indexing, the memory goes back down, no?
On Sat, Sep 5, 2009 at 4:33 AM, Bernhard<email address hidden> wrote: /bugs.launchpad .net/bugs/ 381064
> Yes, it works much better. I might get re-indexing spikes of 0.5 MB with
> ff-mem-fix, but much better than the 10 MB spikes in current trunk.
>
> --
> [bzr] Firefox plugin eats a lot of memory
> https:/
> You received this bug notification because you are a bug assignee.
>
> Status in GNOME Do Plugins Project: In Progress
>
> Bug description:
> Since rev 1195 I feel like docky leaks a lot more memory. It goes up to 300MB if I wait 2 hours. I will attach a debug of events during which the memory usage went from 40MB to 130MB.
>
> EDIT: after further testing, it seems like the firefox plugin (bzr of May 27) is the problem.
>