Pidgin 2.5.1 system-crashing memory leak

[Nanley Chery]

Binary package hint: pidgin

Ubuntu 8.10 beta [upgrade from 8.04.1]
-----------------------------------------------------
pidgin:
  Installed: 1:2.5.1-0ubuntu2
-----------------------------------------------------
I left pidgin open for a couple hours after playing Open arena, using Firefox, and Liferea.
My system began reacting sluggishly, nm-applet restarted, and after checking System Monitor, I saw that Pidgin used up 2.9GB of my 3GB ram. I had to force shutdown, so I was not able to gather any information?
I haven't been able to reproduce this yet.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/pidgin
Package: pidgin 1:2.5.1-0ubuntu2
ProcEnviron:
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin
Uname: Linux 2.6.27-4-generic x86_64

[Philip Peitsch (philip-peitsch)]

I don't think this bug is a duplicate. I'm getting the same behaviour even when the sound is muted.

[Jeremy Visser (jeremy-visser)]

Even if your ALSA device is muted, I think the problem is that Pidgin is talking to PulseAudio, which for some reason can't talk to ALSA. The PulseAudio gstreamer plugin is queuing up all the sound events, waiting for the ALSA device to become free. ALSA devices receive audio data whether they are muted or not.

[Philip Peitsch (philip-peitsch)]

Sorry, I didn't clarify. Me mean even when I have the sound muted in pidgin, I see this behaviour.

[Pedro Villavicencio (pedro)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. You reported this bug a while ago and there hasn't been any activity in it recently. We were wondering is this still an issue for you? Could you try to reproduce the same with Ubuntu 8.10 or 9.04? Thanks in advance.

[Pedro Villavicencio (pedro)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to New. Thanks again!.