Version: (using Devel) OS: Linux Installed from: Compiled sources I'm using KDE SC 4.4RC1 and Kopete eats way too much RAM... I didn't notice this before so it's probably some 4.4 thing. Here it is the relevant ps line $ ps auxf |grep kopete 1638925471 10169 0.3 4.1 765376 163556 ? Sl Jan18 8:36 kopete 4.1% of my 4GB RAM (+ swap), ~160MB for kopete it's IMO too much, giving that - I'm using only one jabber account with ~150 contacts - kmail uses slightly less memory with 6 IMAP accounts - amarok uses 1/4th memory!
Please tell us which Kopete plugins do you use, which jabber server and if you use jabber transports or some special features.
Thanks for the answer. I did an experiment and started with a naked off kopete (no plugin at all) 1638925471 5622 4.9 1.1 410672 47760 ? Sl 08:05 0:01 kopete ~47MB. Could be better but fair enough. Then I started adding back one by one every plugin I had running before + Kubuntu's "Message Indicator Plugin: ~60MB + History ~60MB + Statistics ~61MB + OTR ~69MB So it's using now about an half of memory it was using before, I'll leave this session opened to see if there's some memleak. As of writing it's using already ~74MB. Jabber server it's a private jabberd2 server (Debian Etch). No transports, only local XMPP accounts.
Sorry I forgot to mention the Now Playing plugins, it was started between History and Statistics. Numbers are still correct
Using Kopete 1.0 (with KDE SC 4.4.0 final) now and after 24h started, it's using 81MB. Don't know if this should considered normal or not. What's your opinion?
Well if you have a lot of contacts then it can be normal ... but if the memory grows over time then it's memory leak.
I can confirm this memory leak. Kopete will slowly nibble at my RAM and eat up to 1 GB (25%) in my installation (at which time I notice everything is *very* slow and kill Kopete). When Kopete has just started and logged in to the four (three) services the memory consumption is 13576 k (shared: 34424 k) according to the system activity monitor. I only have 22 contacts, so it's not a problem related to that. Config: 1 Jabber account using SSL, standard server (jabber.no) 1 ICQ account using standard server (login.icq.com) 1 MSN account using standard server (messenger.hotmail.com) 1 Bounjour account
Dear Bug Submitter, This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This is a reminder that this bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
(In reply to Andrew Crouthamel from comment #8) > Dear Bug Submitter, > > This is a reminder that this bug has been stagnant for a long time. Could > you help us out and re-test if the bug is valid in the latest version? Unfortunately I am currently using a Dell XPS 13 with Ubuntu, and therefore I cannot re-test.
(In reply to Kjetil Kilhavn from comment #9) > Unfortunately I am currently using a Dell XPS 13 with Ubuntu, and therefore > I cannot re-test. On second thought, would it be sufficient that I perform the test in VirtualBox? If so, are there any prepared images - or could I for instance use openSUSE Leap or Tumbleweed? I can do that, that's a small effort compared to what all you developers do.
(In reply to Kjetil Kilhavn from comment #10) > (In reply to Kjetil Kilhavn from comment #9) > > Unfortunately I am currently using a Dell XPS 13 with Ubuntu, and therefore > > I cannot re-test. > On second thought, would it be sufficient that I perform the test in > VirtualBox? If so, are there any prepared images - or could I for instance > use openSUSE Leap or Tumbleweed? I can do that, that's a small effort > compared to what all you developers do. Any help is appreciated, so a Tumbleweed VM or something like that would work. Thanks for offering!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
I have tried Kopete today. Unfortunately it seems I don't have any working accounts. My old ICQ handle isn't valid as far as I know, and although my Jabber account should be valid it seems the server isn't doing so well, so I'm not connected. However, that should probably not make much difference with regards to the memory leak, right? Anyway, as you can see below there is at least not any major memory leak caused just by having Kopete running. I left it running , and noted the memory use according to System Monitor I noticed that the memory increased by a few MB if I opened the "About" window, so I made sure that only the main window was open when I noted the memory usage. 79,0 MB (10:33 ) 82,4 MB (11:02) 79,8 MB (23:15) machine mostly idle since 11:02 Kopete is in version 1.13.0 on my system. Test environment (my main computer) Operating System: openSUSE Leap 15.4 KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.90.0 Qt Version: 5.15.2 Kernel Version: 5.14.21-150400.24.38-default (64-bit) Graphics Platform: Wayland Processors: 8 × 11th Gen Intel® Core™ i7-1165G7 @ 2.80GHz Memory: 31.1 GiB of RAM Graphics Processor: Mesa Intel® Xe Graphics
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!