Evolution crash on large IMAP move

Bug #662794 reported by iMac
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
evolution (Ubuntu)
Expired
Low
Unassigned

Bug Description

Binary package hint: evolution

I was unable to move an email to an IMAP subfolder with about 226 emails already in it. The folder was on Courier IMAP (Debian Stable 4.4.0-2) with SSL encryption enabled on the client and server. The email had a single photo (JPG) attached with a size of 7.8MB as shown in the evolution "size" column.

Server bandwidth was approximately 1 mbit / 100KB. The problem was 100% repeatable from . I ended up using my Android Phone IMAP client (K9) to move the message out of my INBOX, so the issue appears to be client specific.

I have two full backtraces attached, which I attempted to capture independent of any other actions (i.e. executed just following a manual Send/Receive) to rule out timeouts related to parallel activities.

Once the email was moved out of my INBOX, evolution seemed to be able to move between other folders without issue.

I have my Evolution set to not expunge automatically.

ProblemType: Bug
DistroRelease: Ubuntu 10.10
Package: evolution 2.30.3-1ubuntu7
ProcVersionSignature: Ubuntu 2.6.35-22.34-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
NonfreeKernelModules: fglrx
Architecture: amd64
Date: Mon Oct 18 12:21:35 2010
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
SourcePackage: evolution

Revision history for this message
iMac (imac-netstatz) wrote :
Revision history for this message
iMac (imac-netstatz) wrote :

After using another client to move the email successfully, I am unable to reproduce with evolution. (moving back to INBOX, and then back into the folder, etc. works fine) One observation I would like to note, is that previously when the issue was occuring, evolution seemed to try to "upload" the email when moving it. i.e. the bandwidth was consumed during the transaction up until several seconds prior to the move failing with an error message. I didn't expect this as it was similar to moving between accounts on different IMAP servers (where it would need to download and re-upload). Now in subsequent tests using the same email, it moves instantly like I would expect (email payload is not transferred between client and server) between any folders on the server side.

I should also note that the issue was 100% repeatable across system reboots previously _ I had tried moving it on various days at the office until I finally captured the session and backtrace to report this issue.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

that might be a libssl crash, could you install the evolution-data-server, evolution and libssl dbgsym packages and get a new backtrace? thanks.

Changed in evolution (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
iMac (imac-netstatz) wrote :

I have the symbols installed, but I was unable to re-create this issue even using an "Edit as New" of the original email and sending from another account to the one where it was originally received.

Added the additional dbgsym packages but unable to get a new backtrace until the next occurance.

Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for evolution (Ubuntu) because there has been no activity for 60 days.]

Changed in evolution (Ubuntu):
status: Incomplete → Expired
Revision history for this message
iMac (imac-netstatz) wrote :

I tracked this issue down to some faulty failover logic that triggered on high load on the multi-homed connection I am using. The failover was seemingly transparent for short transactions, but as the public IP changed during this large IMAP activity, the result was a crash. It may have failed over and back to cause the crash, but since the failover logic was corrected, and is no longer repeatable due to the impact to this particular environment, I will not be able repeat. Not likely to occur again, but worth noting just in case somebody trips over this scenario again (perhaps switching between wifi and 4g).

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.