| Summary: | Manual Filtering Crashes Arbitrarily | ||
|---|---|---|---|
| Product: | [Applications] kmail | Reporter: | Gary Krueger <kde> |
| Component: | IMAP | Assignee: | kdepim bugs <kdepim-bugs> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | christophe, dominik.tritscher |
| Priority: | NOR | Keywords: | triaged |
| Version: | 1.9.7 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
|
Description
Gary Krueger
2007-09-17 17:08:49 UTC
By the way, these are e-mail messages in the KMail component. Considering the current state of KMail filters (won't auto filter, crashes on manual filtering), I've found that the half reasonable way to process hundreds of messages through the filters, is to do the following: Start processing some messages (Ctrl-J), so that you can click on the up arrow next to the download progress bar at the bottom right corner. Then, hit Ctrl-J once each time you see it transition to showing either zero or one thread boxes. You don't have to wait until it stabilizes to zero or one thread boxes. Just wait until it transitions to zero or one thread boxes. That way, you can manage to process one or two hundred messages before KMail crashes. Otherwise if you do it any other way, you can expect it to crash typically after processing less than a dozen messages. Using this method to circumvent the problem, I've discovered that the filters are generating multiple (2-6) download threads for individual messages. That is, a message for "V169r6" may appear several times in the list of threads when the up arrow next to the download progress bar is clicked (open). Well, I can OFTEN process one or two hundred messages waiting for a zero or one thread box transition. But, better results can be had by waiting for a zero thread transition. My first 2 filters add to the message headers. The subsequent filters act upon those added message headers. It appears that the filtering attempts to use multiple threads to process the filters in parallel. But, reader threads must be blocked while writer threads (such as the Pipe Through action) proceed. But, this requires knowing which threads are writer threads before starting any threads. This may be key to solving many of the filtering issues (manual and automatic). This issue goes away for me when I downgrade kdepim (kmail) to 1.9.4. I didn't experienced any problems with filtering using kmail 1.11.90 built from trunk. (In reply to comment #7) > I didn't experienced any problems with filtering using kmail 1.11.90 built from > trunk. Fine, let's close this report then. Feel free to open a new report if you experience a similar bug with KMail > 1.11.4 |