Bug 95461 - kmail gets oom killed when moving large numbers of mails between folders
Summary: kmail gets oom killed when moving large numbers of mails between folders
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kmail
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR major
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 98337 (view as bug list)
Depends on:
Blocks:
 
Reported: 2004-12-19 16:23 UTC by goertzen
Modified: 2015-04-12 11:20 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description goertzen 2004-12-19 16:23:57 UTC
Version:           3.3.1 (using KDE KDE 3.3.1)
Installed from:    Gentoo Packages
Compiler:          gcc version 3.3.4 20040623 (Gentoo Linux 3.3.4-r1, ssp-3.3.2-2, pie-8.7.6) 
OS:                Linux

I have an imap folder with ~13,000 spam emails.  When I select them all and drag them to a local folder, kmail uses all available memory and eventually gets oom killed.  As a work around, moving a few hundred at a time seems to be working but is laborious.  Thunderbird on MS windows was able to move all messages at once from a local folder to the imap folder, so kmail should be able to do similar without oom-ing.

I have another folder with ~50,000 spams I would like to move too!

My system is a Duron 1300 with 256M of ram.

Kmail goes Kaboom:

Dec 19 08:49:49 super oom-killer: gfp_mask=0xd2
Dec 19 08:49:49 super DMA per-cpu:
Dec 19 08:49:49 super cpu 0 hot: low 2, high 6, batch 1
Dec 19 08:49:49 super cpu 0 cold: low 0, high 2, batch 1
Dec 19 08:49:49 super Normal per-cpu:
Dec 19 08:49:49 super cpu 0 hot: low 26, high 78, batch 13
Dec 19 08:49:49 super cpu 0 cold: low 0, high 26, batch 13
Dec 19 08:49:49 super HighMem per-cpu: empty
Dec 19 08:49:49 super
Dec 19 08:49:49 super Free pages:         640kB (0kB HighMem)
Dec 19 08:49:49 super Active:54332 inactive:797 dirty:0 writeback:10 unstable:0 free:160 slab:2741 mapped:51803 pagetables:359
Dec 19 08:49:49 super DMA free:64kB min:32kB low:64kB high:96kB active:11600kB inactive:12kB present:16384kB
Dec 19 08:49:49 super protections[]: 0 0 0
Dec 19 08:49:49 super Normal free:576kB min:456kB low:912kB high:1368kB active:205728kB inactive:3176kB present:229312kB
Dec 19 08:49:49 super protections[]: 0 0 0
Dec 19 08:49:49 super HighMem free:0kB min:128kB low:256kB high:384kB active:0kB inactive:0kB present:0kB
Dec 19 08:49:49 super protections[]: 0 0 0
Dec 19 08:49:49 super DMA: 6*4kB 1*8kB 0*16kB 1*32kB 0*64kB 0*128kB 0*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 64kB
Dec 19 08:49:49 super Normal: 26*4kB 5*8kB 1*16kB 1*32kB 0*64kB 1*128kB 1*256kB 0*512kB 0*1024kB 0*2048kB 0*4096kB = 576kB
Dec 19 08:49:49 super HighMem: empty
Dec 19 08:49:49 super Swap cache: add 461077, delete 458736, find 137352/200807, race 0+5
Dec 19 08:49:49 super Out of Memory: Killed process 14977 (kmail).
Comment 1 Thiago Macieira 2004-12-19 16:26:58 UTC
This isn't a crash.
Comment 2 Danny Kukawka 2005-01-28 19:20:31 UTC
'This isn't a crash.' But there is a memory leak in KMail ... same problem, if you import many messages with KMailCVT. see Bug: #81634
Comment 3 Thiago Macieira 2005-01-28 22:29:54 UTC
Memory leak isn't a crash. We use a strict definition of "crash" in bugs.kde.org: receiving a signal and dumping core -- the KDE Crash Handler appears.

This is only a semantic issue. It doesn't mean your bug is grave.
Comment 4 Danny Kukawka 2005-01-28 22:57:24 UTC
Yes I know the difference between a crash and a memory leak. I wanted only point  to the reason of the bug.
Comment 5 Danny Kukawka 2005-02-03 00:20:42 UTC
*** Bug 98337 has been marked as a duplicate of this bug. ***
Comment 6 Danny Kukawka 2005-04-01 12:54:04 UTC
Is this maybe the same problem like in bug #81634 ? For the problem with memory at import there is a fix (http://webcvs.kde.org/kdepim/kmail/kmkernel.cpp?rev=1.329&view=log). Maybe adapt this patch ?
Comment 7 Björn Ruberg 2009-12-20 16:37:10 UTC
Is this still valid?
Comment 8 RussianNeuroMancer 2011-02-15 06:52:36 UTC
No.
Comment 9 Laurent Montel 2015-04-12 10:00:59 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.