Bug 341746 - Deleting a search folder puts kontact/kmail2 in dire state and finally crashes the Application
Summary: Deleting a search folder puts kontact/kmail2 in dire state and finally crashe...
Status: RESOLVED DUPLICATE of bug 349789
Alias: None
Product: kmail2
Classification: Applications
Component: search (show other bugs)
Version: Git (master)
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-12-10 15:44 UTC by Rigo Wenning
Modified: 2016-07-12 07:55 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Rigo Wenning 2014-12-10 15:44:38 UTC 
Deleting virtual folders makes the imap- folder list disappear for at least 5 minutes without optical feedback that kmail2 is working. Once the folder list comes back, kmail2 is in a dire state and will ultimately crash with 100% on one of the cores. 

Reproducible: Always

Steps to Reproduce:
To reproduce: 
1. Start a search in your imap - account in some folder (or all). 
2. Accept to create a virtual folder (last-search). 
3. Search (completes without problems)
4. After the search, look at some messages. 
5. Then delete this virtual folder (last search)

Actual Results:  
Now the imap - account disappears from the folder-list (left) and eventually re-appears after 5-6 minutes (seems to depend on how large the imap account is). No feedback on processing is given. Now kmail2 is in a dire state. Some new arbitrary folder appears in the favorites. After some time, kmail2 starts using 100% of one core. 

Expected Results:  
The virtual folder is deleted without re-processing everything and kmail remains in a stable state. 

Luc Montel confirmed the behaviour and said it has to do with the ETM
Comment 1 Laurent Montel 2014-12-10 15:47:09 UTC 
It's an ETM bug.
Christian knows this class.
Comment 2 David Faure 2016-07-12 07:55:48 UTC 
Turned out to be a KRecursiveFilterProxyModel bug, actually.
Fix coming up.

*** This bug has been marked as a duplicate of bug 349789 ***