Version: 1.0.0 (using KDE 4.4.1) OS: Linux Installed from: Ubuntu Packages I recently added a second GTalk account to my configuration. I had my normal gmail jabber account, then I added a second one which belongs to a company which hosts its email in google. After that, Kopete started leaking memory or at least it looks like that. If I leave it on when I end my shift, I come back next morning to find Kopete is taking over 1GB of RAM. At home, the opposite happens, I come back from work and it's taking over 2GB (my home PC has more RAM). It only started happening after adding this second account.
Seems like I have the same bug. Kopete 1.0.0, KDE 4.4.3. Uses 212 Mb after 24 hours. I have two accounts, both jabber, one of which is Gmail chat.
Same happens here, memory usage just starts climbing from the get-go - after < 1 hour, I have kopete using 180 mb memory, and if I leave it on over night, it consumes all available memory and grinds everything to a halt (mainly because of memory swapping) I have two jabber accounts (gmail and facebook), and an msn account active.
This happens on kde 4.5 packages, kubuntu.
I have this problem too. I have two jabber accounts, one msn account and icq account. I have opensuse 11.3, kopete is 1.0.0 and KDE 4.4.4. Over night it consumes all memory (3GB) and computer is swapping.
I have this problem too, its memory increases at each reconnection, more and more each time. It's about 2 Mo per reconnection at the beginning. I use 4 accounts (2 jabber, 1 icq, 1 msn). Kopete 1.0.80, KDE 4.5.2, Kubuntu 10.10.
same here on 2 kubuntu systems, kde-4.4.2 and kopete 1.0.0
Same problem with Kopete 1.0.80, KDE 5.4.1 (Kubuntu) on multiple machines.
4.6.1 — the same. After two hours RSS ~300 Mb. Two jabber accounts, one oscar.
After I added a Skype account, Kopete started using 700 MB - 1 GB of RAM, even when the Skype account is offline. KDE 4.6.0, Kopete 1.0.80, openSUSE packages
Created attachment 62184 [details] Valgrind massif profile I had noticed behaviour like the bug described here after accidentally leaving Kopete logged in at work over a weekend. Over that time Kopete proceeded to consume multiple GBs of RAM. I have three jabber accounts - two are GTalk, but only one of those two is set to log in. (FWIW, I additionally have two WLM and a Yahoo account.) I took a valgrind massif profile of the behaviour, and have attached it. To my untrained eye, it seems to be a problem within the certificate subsystem. Hope that helps.
Same issue, but only one jabber account and one ICQ. Memory usage increases of cca. 2 MB each time jabber is connecting (doesn't matter whether SSL is used or not). My jabber server is sick today, it is disconnecting me each few seconds and so Kopete eats hundreds of MB in two hours.
Thank you for the bug report. As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists. If this bug is no longer persisting or relevant please change the status to resolved.