Bug 708619 - [abrt] claws-mail-3.7.9-2.fc14: mimeview_show_message: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Summary: [abrt] claws-mail-3.7.9-2.fc14: mimeview_show_message: Process /usr/bin/claws...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: claws-mail
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Andreas Bierfert
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0e69a4195a1f6e2625e1174fcd0...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-28 12:00 UTC by David Kovalsky
Modified: 2014-03-31 23:46 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 12:06:58 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (40.99 KB, text/plain)
2011-05-28 12:00 UTC, David Kovalsky
no flags Details

Description David Kovalsky 2011-05-28 12:00:25 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 41973 bytes
cmdline: claws-mail
comment: I tried reproducing this during a large `yum update' transaction, but I can't trigger this again. Perhaps this is some kind of race conditidion (I have a 4 core / 8 threads CPU) which is hard to hit (?).
component: claws-mail
Attached file: coredump, 2368749568 bytes
crash_function: mimeview_show_message
executable: /usr/bin/claws-mail
kernel: 2.6.35.13-91.fc14.x86_64
package: claws-mail-3.7.9-2.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1306583154
uid: 10625

How to reproduce
-----
1. I selected 2-3 emails (in a thread), right cliked and wanted to delete. But the mouse pointer slipped to reply and 2-3 reply windows popped up. I immediately started clicking the 'exit' button in the top right corner ('X'), but the windows didn't go away. 

2. The reply windows didn't disappear immediately, maybe because the computer was under load for a second there. So I clicked the quit 'X'es in the top right corner again once or twice.

3. At this point the UI seemed to be frozen and switching to the main windows the UI didn't get redrawn. Almost immediately claws crashed and abrt came up.

Comment 1 David Kovalsky 2011-05-28 12:00:29 UTC
Created attachment 501467 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-05-28 13:17:59 UTC
> Perhaps this is some kind of race condition

Wouldn't surprise me. For example, some weeks ago I've filed this analysis:
http://www.thewildbeast.co.uk/claws-mail/bugzilla/show_bug.cgi?id=2398

And mimeview_destroy is threaded, too.

Comment 3 Fedora End Of Life 2012-08-16 12:07:01 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.