I was recently able to reproduce the symptom from the comment I posted
on 2007-07-27 using n-d trunk, so I don't believe it's fixed
upstream. Using valgrind I tried to identify the leak but was unable.
Anything I can do to help further?
On Tue, Apr 15, 2008 at 9:27 AM, Sebastien Bacher <[EMAIL
Having upgraded to Gutsy I can verify this bug is still preset. Any
ideas? I'd be willing to look into this further but would probably
need some guidance.
On 9/18/07, Brian Fallik <[EMAIL PROTECTED]> wrote:
> Is there an easy way to test 0.3.7 on Feisty? Download n-d and build
> the source? Ba
Is there an easy way to test 0.3.7 on Feisty? Download n-d and build
the source? Backport Gutsy's? Etc?
I can also just wait for Gutsy.
On 9/13/07, Brian Fallik <[EMAIL PROTECTED]> wrote:
> Could be. That's in 0.3.7 (gutsy); eft is at 0.3.6.
>
> On 9/12/07, shacharr <[EMAIL PROTECTED]> wrote:
Could be. That's in 0.3.7 (gutsy); eft is at 0.3.6.
On 9/12/07, shacharr <[EMAIL PROTECTED]> wrote:
> http://trac.galago-project.org/changeset/2971
>
> Maybe this changeset will help?
>
> The relevant bug report ( http://trac.galago-project.org/ticket/105 )
> talks about a memory leak fixed.
>
>
On 5/13/07, Andrew Conkling <[EMAIL PROTECTED]> wrote:
>
> In the meantime, it might be worth mentioning some specifics on my system:
> thinking of things that use libnotify, I'm running Pidgin with the libnotify
> plugin, Rhythmbox with song change notifications on, and the ZeroConf
> Service Disc
On 5/13/07, Sebastien Bacher <[EMAIL PROTECTED]> wrote:
>
> Getting a valgrind log would be useful to spot an incorrect usage
Would this still be useful if the memory usage isn't ridiculously extreme?
Currently n-d is using 22 MB, which still seems extreme than the 1 or 2 MB
it uses when I first
