Bug 688921

Summary: [abrt] claws-mail-3.7.8-6.fc13: _int_malloc: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Alessandro Nazzani <alessandro.nazzani>
Component: claws-mailAssignee: Andreas Bierfert <andreas.bierfert>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 13CC: andreas.bierfert, bugs.michael, tomspur
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:54fae1d9a771c819a9da9d2ac7ef4863eef6fcec
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-18 15:30:00 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Alessandro Nazzani 2011-03-18 14:26:45 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: claws-mail
component: claws-mail
crash_function: _int_malloc
executable: /usr/bin/claws-mail
kernel: 2.6.34.8-68.fc13.i686.PAE
package: claws-mail-3.7.8-6.fc13
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1300458154
uid: 500

How to reproduce
-----
1. I was fetching messages from my accounts
2. I think there was a short (2 o 3 secs) network connection interruption
3. Claws apparently hanged, so I tried to close it and after some seconds it crashed
Comment 1 Alessandro Nazzani 2011-03-18 14:26:49 UTC 
Created attachment 486255 [details]
File: backtrace
Comment 2 Michael Schwendt 2011-03-18 14:40:57 UTC 
> Claws apparently hanged

How long did you wait? You can configure the Socket I/O Timeout in the Preferences > Other > Miscellaneous. Only if it doesn't recover from network interruption automatically after the timeout, it would be a real freeze.

Anyway, interrupting IMAP activity is known to cause trouble in Claws Mail. There are other/similar bug reports about it.
Comment 3 Alessandro Nazzani 2011-03-18 14:54:03 UTC 
> How long did you wait?

Don't remember exactly, 20/30 seconds maybe.

> You can configure the Socket I/O Timeout in
> the Preferences > Other > Miscellaneous.

It's 60 secs currently (the default?).

Anyway, thanks for your reply.

Alessandro
Comment 4 Michael Schwendt 2011-03-18 15:30:00 UTC 

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