Bug 384772

Summary: kAddressbook 5.6.1: Excessive memory consumption
Product: [Applications] kaddressbook Reporter: Gunter Ohrner <kdebugs>
Component: generalAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED FIXED    
Severity: normal CC: tokoe
Priority: NOR    
Version: 5.6.0   
Target Milestone: ---   
Platform: Neon   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Gunter Ohrner 2017-09-16 16:18:40 UTC 
kAddressbook 5.6.1 consumes rediculous amounts of memory on my system - it took a minute or so to start and now consumed 5,2 GB RSS, while akonadiserver consumes additional 1,3 GB and the corresponding mysqld process 1,1 GB...

  PID USER      PR  NI    VIRT    RES    SHR S  %CPU %MEM     ZEIT+ BEFEHL                                                                    
 4232 gunter    20   0 6487468 5,195g  80592 S   0,0 44,7   0:49.83 kaddressbook                                                              
 3218 gunter    20   0 3854248 1,313g   3428 S  11,3 11,3   0:10.87 akonadiserver                                                             
 1566 mysql     20   0 3655660 1,115g   7784 S  33,9  9,6   1:01.60 mysqld                                                                    

The system has 12 GB, but an RSS size of this is not common and the system started paging memory to SSD.

I only have one local addressbook defined with a three-digit number of entries.
Comment 1 Gunter Ohrner 2017-09-16 16:20:13 UTC 
Addendum: After a while the memory consumption "normalized" to 244 MB (still much for such a "small" application, but acceptable):

4232 gunter    20   0 6487468 244268  80592 S   0,0  2,0   0:50.85 kaddressbook
Comment 2 Gunter Ohrner 2017-09-16 16:23:15 UTC 
Note: VIRT is still more than 6 GB, but the space does not seem to be actually used, it's also not paged out. Swap space usage at the moment is about 1 GB in total.
Comment 3 Justin Zobel 2022-11-10 08:52:32 UTC 
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!
Comment 4 Gunter Ohrner 2022-11-11 18:44:28 UTC 
Seems to be fixed in current version.