Bug 646591

Summary: [abrt] evolution-2.32.0-2.fc14: vee_folder_sync: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Mathieu Bridon <bochecha>
Component: evolutionAssignee: Matthew Barnes <mbarnes>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: i.mortimer, lucilanga, mbarnes, mcrha, poc
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f440d9391c55a15a6b5b5c9f590f0207fa81d33b
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-11-08 09:51:26 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace
none
Evo status bar during infinite wait none

Description Mathieu Bridon 2010-10-25 18:09:18 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: evolution
component: evolution
crash_function: vee_folder_sync
executable: /usr/bin/evolution
kernel: 2.6.35.6-45.fc14.x86_64
package: evolution-2.32.0-2.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1288029556
uid: 500

How to reproduce
-----
1. Opened Evolution
2. Tried to look at my emails
3. Fetching was **very** slow, and trying to view other emails/inboxes just piled operations
4. Evolution crashed
Comment 1 Mathieu Bridon 2010-10-25 18:09:21 UTC 
Created attachment 455597 [details]
File: backtrace
Comment 2 Patrick O'Callaghan 2010-11-05 23:10:33 UTC 
Package: evolution-2.32.0-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Start Evo, configured for several IMAP servers including Gmail
2.Use for a while
3.Crash occurs after a long wait in autorefresh


Comment
-----
The Gmail account has several large folders (including the Fedora Users and Test lists going back several years).
I noticed that occasionally the Users list would appear to stick at "getting new mail: 100%". Meanwhile the rest of
Evo is unresponsive, i.e. the interface still reacts to clicks but no new mail can be viewed, even in different
folders or accounts from the one affected. After leaving the session running overnight, I returned to find it
had crashed. The Gmail account is set to refresh every 15 minutes. The other IMAP account refreshes every
10 minutes.
Comment 3 Patrick O'Callaghan 2010-11-05 23:25:11 UTC 
Created attachment 458256 [details]
Evo status bar during infinite wait

This is a typical example of the Evo status bar prior to the crash. It can stay like this "forever". The three panes represent: 1) Refreshing the Fedora Announce list folder (which has one new message at this point), 2) Fetching a *local* message for viewing (from an "On This Computer" mbox), and 3) Updating summary info for the large (~50k messages) Fedora Users folder. None of these actions reaches completion, even though number 3 is at 100%.
Comment 4 Patrick O'Callaghan 2010-11-05 23:26:44 UTC 
(In reply to comment #2)

> I noticed that occasionally the Users list would appear to stick at "getting
> new mail: 100%".

I should have said "Updating summary information for new messages (100% complete)"
Comment 5 Patrick O'Callaghan 2010-11-06 22:20:31 UTC 
Package: evolution-2.32.0-2.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Start Evolution
2.
3.


Comment
-----
I started Evo and allowed it to refresh existing accounts with no interaction, not even viewing existing mail.
Again it stuck at the "updating summary ... 100%" point as reported before, and subsequently crashed.
Comment 6 Milan Crha 2010-11-08 09:51:26 UTC 

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