Bug 142917

Summary:	kio_imap4 has memory leak when using DIMAP
Product:	[Unmaintained] kmail	Reporter:	Vladimir <vladimir.elisseev>
Component:	IMAP	Assignee:	kdepim bugs <kdepim-bugs>
Status:	RESOLVED UNMAINTAINED
Severity:	normal	CC:	ahoward, da, sergiosdj, vladimir.elisseev, vovochka13
Priority:	NOR
Version:	unspecified
Target Milestone:	---
Platform:	Gentoo Packages
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vladimir 2007-03-13 13:51:17 UTC

Version:            (using KDE KDE 3.5.6)
Installed from:    Gentoo Packages
Compiler:          gcc-4.1.2 
OS:                Linux

I noticed that after a while kmail synchronizing mail folders (DIMAP) slower and slower, so I checked memory usage and have been quite surprised. I have two mailboxes defined in KMail (DIMAP and normal IMAP), both of them are starting with about the same amount of memory like below:

  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
29955 vovan      0   0 43348 7532 5392 S    0  0.7   0:04.40 kio_imap4

but after ~one day the first one is consuming the same amount of memopry but the second with DIMAP is using:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
22273 vovan      0   0 74468  37m 5368 S    0  3.7   9:06.28 kio_imap4

The memory amount kio_imap4 uses is growing almost linearly even without any activities (except checking for a new mail)  and in one week eats almost all memory I have.

Comment 1 Vladimir 2007-05-18 13:59:18 UTC

bump... still the same situation. I've heard that lot of users are experienced DIMAP slowness and I assume most of them because this memory leak... they just don't realize this.

Comment 2 Rainer Sabelka 2007-11-22 21:13:19 UTC

Same problem here (using kmail 1.9.6 from opensuse-10.3 with dimap)
When I start kmail:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
23343 saba      15   0  140m 7608 4944 S    1  0.2   0:00.54 kio_imap4

After a some days:
  PID USER      PR  NI  VIRT  RES  SHR S %CPU %MEM    TIME+  COMMAND
 4139 saba      15   0  872m 739m 4952 S    0 18.8   2597:24 kio_imap4

Comment 3 Vladimir 2007-11-23 07:02:18 UTC

I think developers are too busy with KDE4/QT4 migration at the moment, but I wouldn't be surprised if this bug will be presented in the new version. That's the only explanation I could find at the moment. Memory leak _is_ a serious bug, but it's more then 7 month old already, nobody out of KDE team cares!!!

Comment 4 Allen Winter 2007-11-23 14:41:12 UTC

Actually, we do care. We care very much.

kio_imap4 has gotten some attention for KDE4 release. I know for sure that Matt made a few changes related to memory leaks. So there is hope for solving this bug.

Please don't say we don't care.

Comment 5 Vladimir 2007-11-23 14:56:02 UTC

Sorry, for the not polite post. Finally, the bug status changed to "NEW" and we have a hope.

Comment 6 Matt Rogers 2007-11-23 15:18:37 UTC

I've fixed a few memory leaks in kio_imap4 already, so it should be better. They're not all fixed yet, but as I continue to find them, I'll continue to fix them.

Comment 7 Vladimir 2007-11-23 16:59:05 UTC

Are you talking only about KDE4? If that so, is it a lot of work to backport them to KDE3?

Comment 8 Vladimir 2009-05-07 11:01:24 UTC

The bug is still presented in the latest KDE 4.2.3 as well as in KDE 3.5.10. This bug report is more then two years old at the moment :)

Comment 9 Danny Auble 2009-09-02 22:06:39 UTC

This bug still appears to be present in kde 4.3.1.  It would be nice to not have to restart every once in a while because all my memory is gone.

Comment 10 Vovochka 2009-09-14 04:56:05 UTC

Is anybody going to do somthing with this? :)

Comment 11 Austin Howard 2009-12-09 00:37:33 UTC

This bug is still present in my installation of KDE 4.3.2.

Comment 12 Danny Auble 2009-12-09 00:40:38 UTC

as it is in 4.3.4

Comment 13 Vovochka 2009-12-23 02:56:58 UTC

Will it ever be fixed? It's really annoying.

Comment 14 Vladimir 2009-12-23 06:45:16 UTC

(In reply to comment #13)
> Will it ever be fixed? It's really annoying.
To be honest, I don't think so. This bug report is more then 2,5 years old, but the bug is more then 3 years old (I'm not the first one who has reported the bug).

Comment 15 Vovochka 2009-12-23 07:02:43 UTC

Memory leaks is one of the main kde problem. And it's really disappointing that such bugs have so low priority between developers.

Comment 16 Sérgio Durigan Júnior 2010-04-28 22:37:45 UTC

Pinging the bug to see if someone looks at it.  I'm still facing this problem on KDE 4.4.2.

Comment 17 Vovochka 2010-04-28 23:56:06 UTC

May be it's better to open a new bug?

Comment 18 Laurent Montel 2015-04-12 10:07:26 UTC

Thank you for taking the time to file a bug report.

KMail2 was released in 2011, and the entire code base went through significant changes. We are currently in the process of porting to Qt5 and KF5. It is unlikely that these bugs are still valid in KMail2.

We welcome you to try out KMail 2 with the KDE 4.14 release and give your feedback.