On Thu, 2009-02-05 at 23:32 +0000, Richard Seguin wrote: > What I am curious about is why my up to date intrepid doesn't produce > the same thing...
Uhm. That valgrind log is from up-to-date Intrepid. That valgrind log is only from a short period of time and you can clearly see the leaks it produced. Pidgin crashes on me every 2-3 days as it ends up getting ENOMEM at 1GB of VM due to memory leaks. > Have you tried moving your .purple directory to > something else and letting pidgin setup from scratch again? No. But why do we need to do that. You now have a valgrind log in hand that shows you exactly where the memory is leaking. What was the point of collecting the valgrind log if we are going to go through one of these "stab-in-the-dark" debugging processes where we try enabling/disabling everything one-by-one until we find a culprit? > I am still a little reluctant at this point to mark this as triaged as > there hasn't been much trouble shooting to see what's causing the > problem. Are you kidding me? Do you know how painful it was to try to be productive with pidgin while valgriding it? I use IRC constantly, all day long to communicate with co-workers. Having it running pitifully slow while being run under valgrind was painful. I take offence at your characterization of it being "little" effort. > Also are you running the 32 bit version of intrepid or the 64 > bit? 32 bit. -- [intrepid] Pidgin at times produces segfault. Valgrind included shows memory leaks. https://bugs.launchpad.net/bugs/321258 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
