Bug 102764

Summary: Mail importer eat ALL the memory
Product: [Unmaintained] kmail Reporter: Sebastien <slaout>
Component: kmailcvtAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED WORKSFORME    
Severity: crash    
Priority: NOR    
Version: unspecified   
Target Milestone: ---   
Platform: unspecified   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Sebastien 2005-03-29 17:54:54 UTC 
Version:            (using KDE KDE 3.4.0)

I've imported all my Evolution mails to KMail.
Unfortunately, my Evolutions mals are 248 Mb!

It seems that once a folder (a mbox file...) is imported, KMailImporter... keep it in memory.
So all RAM was filled little by little.
And then all SWAP was fulled little by little.
And then my computer begined to access disk all the time (perhapse to swap/unswap pages), CPU was unused, while memory and swap was 100% full. System responsiveness was very bad.
After 10 minutes I managed to shutdown my computer without the brute force (to not damage my harddisk: always accessed by the system).

Can you unload from the memory the folders you just imported?
I was obliged to import my mails in two passes:
- Import from Evolution as much as KMail can do
- Stop it
- Delete some folders in my Evolution Inbox
- Restart computer
- Continue to import Evolution mails

And everything was OK.
But it's not what a regular user could have done.
Comment 1 Till Adam 2005-03-30 13:46:25 UTC 
Assigning to correct component. I think it's a duplicate of a fixed issue, though.
Comment 2 Danny Kukawka 2005-03-30 21:53:48 UTC 
How much memory have your machine? Can you try the current cvs version of kmail and kmailcvt? If the mbox is correct and not corrupted this problem should be fixed in the CVS (see: http://webcvs.kde.org/kdepim/kmail/kmkernel.cpp?rev=1.329&view=log ). Which platform you use?
Comment 3 Sebastien 2005-03-30 22:13:28 UTC 
> How much memory have your machine?


512 Mb of RAM.
251 Mb of SWAP.
KMail/kmailcvt 3.4.0
Comment 4 Danny Kukawka 2005-04-01 12:55:31 UTC 
I close the bug, verify please with CVS version and reopen if there is also a problem