pidgin started to swap, taking up a huge amount of memory
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
pidgin (Ubuntu) |
Expired
|
Low
|
Unassigned |
Bug Description
Binary package hint: pidgin
Never seen that before, at least related to sqlite. pidgin sometimes gets as slow as a turtle but it doesn't crash often and when this happens I just click over X (window close button) and xfce asks if I want terminate the application (and I do, because it's rather annoying wait sometimes about 90 seconds or more to be able to type in any pidgin text box).
When this bug happened I had been browsing on internet with Firefox 3.7a1 (and an opened window with Chatzilla 0.9.85) which sometimes has memory leakage, but since applications shouldn't mess with each other because they're should be in different memory addresses (remembering FF does use sqlite too...), this combination shouldn't lead to massive disk swaping. The fun part was: I thought Firefox was doing the swap and I killed it with -9 signal, but memory consumption got steady (and very high, about 1650MiB of RAM and 50MiB of swap space). Then I closed pidgin and it dropped to something as low as 350MiB (not sure now, but it was impressive and it was 3:00am too).
It might be an sqlite problem and not a pidgin one, but I had to report this because of dmesg and ubuntu-bug.
[871744.853704] pidgin[5515]: segfault at 7ffb6b6ad610 ip 00007ffb6b6ad610 sp 00007fff22ef5488 error 14 in libsqlite3.
ProblemType: Bug
Architecture: amd64
CheckboxSubmission: 1dcf98e1af313db
CheckboxSystem: edda5d4f616ca79
Date: Mon Nov 9 16:33:41 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: pidgin 1:2.6.2-1ubuntu7 [modified: usr/bin/pidgin]
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=pt_BR.UTF-8
SHELL=/bin/bash
ProcVersionSign
SourcePackage: pidgin
Uname: Linux 2.6.31-14-generic x86_64
Changed in pidgin (Ubuntu): | |
status: | New → Confirmed |
Thank you for taking the time to report this bug and helping to make Ubuntu better. We are sorry that we do not always have the capacity to look at all reported bugs in a timely manner. There have been many changes in Ubuntu since that time you reported the bug and your problem may have been fixed with some of the updates. It would help us a lot if you could test a current, supported, Ubuntu version. Thanks in advance