[Bug 282502] Re: pidgin memory leak

2008-11-09 Thread Adrian Godoy
Issue disappeared after upgrade to Pidgin 2.5.2. Issue was not reproducible after a specific trigger. Hopefully it was just something particular to my system. ** Changed in: pidgin (Ubuntu) Status: New => Invalid -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received th

[Bug 282502] Re: pidgin memory leak

2008-11-09 Thread Adrian Godoy
Well It has been almost a month since I upgraded to Pidgin 2.5.1 and now im running 2.5.2. The problem has not reoccurred. I have also upgraded to 8.10. The mystery will remain for somebody else to discover, if it has not been fixed yet. -- pidgin memory leak https://bugs.launchpad.net/bugs/2825

Re: [Bug 282502] Re: pidgin memory leak

2008-10-13 Thread Adrian Godoy
Not yet. I will keep you posted. On Mon, Oct 13, 2008 at 4:41 PM, surfed <[EMAIL PROTECTED]> wrote: > and the crash still happens? > > -- > pidgin memory leak > https://bugs.launchpad.net/bugs/282502 > You received this bug notification because you are a direct subscriber > of the bug. > > Status

[Bug 282502] Re: pidgin memory leak

2008-10-13 Thread surfed
and the crash still happens? -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo

[Bug 282502] Re: pidgin memory leak

2008-10-13 Thread Adrian Godoy
I meant intrepid repositories. -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listin

[Bug 282502] Re: pidgin memory leak

2008-10-13 Thread Adrian Godoy
Running pidgin 2.5.1 now. Installed from the hardy repositories. -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https

Re: [Bug 282502] Re: pidgin memory leak

2008-10-12 Thread surfed
can you update pidgin to 2.5.1 ? None are more hopelessly enslaved, than those who falsely believe they are free. J.W. von Goethe Adrian Godoy wrote: > /var/log/messages from that time frame. > > > ** Attachment added: "var_log_messages" >http://launchpadlibrarian.net/18491169/var_log_messag

[Bug 282502] Re: pidgin memory leak

2008-10-12 Thread Adrian Godoy
/var/log/messages from that time frame. ** Attachment added: "var_log_messages" http://launchpadlibrarian.net/18491169/var_log_messages -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed

[Bug 282502] Re: pidgin memory leak

2008-10-12 Thread Adrian Godoy
Ok here is my debug file, well the last 26 lines, and I am also including my /var/log/messages for the same timeframe. ** Attachment added: "pidgin debug output" http://launchpadlibrarian.net/18491162/debug.log -- pidgin memory leak https://bugs.launchpad.net/bugs/282502 You received this bug

Re: [Bug 282502] Re: pidgin memory leak

2008-10-12 Thread surfed
you cut do a tail --lines 25 debug | debug.striped to get the last 25 lines of output None are more hopelessly enslaved, than those who falsely believe they are free. J.W. von Goethe Adrian Godoy wrote: > I am actually running it on the debug window right now. I was running > it in debug mode

Re: [Bug 282502] Re: pidgin memory leak

2008-10-12 Thread Adrian Godoy
I am actually running it on the debug window right now. I was running it in debug mode when it crashed. I did not post the file because it has a lot of personal information. Any suggestions on how to strip that out? On Mon, Oct 13, 2008 at 1:19 AM, surfed <[EMAIL PROTECTED]> wrote: > Could you run

[Bug 282502] Re: pidgin memory leak

2008-10-12 Thread surfed
Could you run pidgin with the "--debug" option? Better even, start pidgin like this: pidgin --debug > debug This will write all debug messages from pidgin to the file "debug" in the directory where you executed pidgin. After your box crashes post relevant part of debug here. -- pidgin memory