Bug 689644 - [abrt] claws-mail-3.7.8-6.fc14: _int_malloc: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
Summary: [abrt] claws-mail-3.7.8-6.fc14: _int_malloc: Process /usr/bin/claws-mail was ...
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:de912a384607039d92b19580aa2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-22 01:15 UTC by Suvayu
Modified: 2012-08-16 12:05 UTC (History)
5 users (show)

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


Attachments (Terms of Use)
File: backtrace (86.00 KB, text/plain)
2011-03-22 01:15 UTC, Suvayu
no flags Details

Description Suvayu 2011-03-22 01:15:50 UTC
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 88061 bytes
cmdline: claws-mail
comment: I have experienced a few crashes like this with F14 before. They seem to be random. The last time I couldn't report to bugzilla because the report said the backtrace is unusuable.
component: claws-mail
Attached file: coredump, 318955520 bytes
crash_function: _int_malloc
executable: /usr/bin/claws-mail
kernel: 2.6.35.11-83.fc14.x86_64
package: claws-mail-3.7.8-6.fc14
rating: 4
reason: Process /usr/bin/claws-mail was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1300756261
uid: 500

How to reproduce
-----
1. I resumed my thinkpad from sleep and claws crashed within a minute of that
2.
3.

Comment 1 Suvayu 2011-03-22 01:15:52 UTC
Created attachment 486711 [details]
File: backtrace

Comment 2 Michael Schwendt 2011-03-22 07:03:48 UTC
> I resumed my thinkpad from sleep

And that makes it likely that Suspend/Resume is the culprit here. The crash is internal to glibc memory allocation (in __libc_malloc (bytes=16) at malloc.c:3660), possibly due to memory corruption.

Comment 3 Michael Schwendt 2011-05-04 21:21:50 UTC
In which ways do you use the Python plugin?

Comment 4 Suvayu 2011-05-28 21:01:17 UTC
Sorry for the late reply, for some reason I wasn't added to the CC list and missed your comments.

I don't use the python plugin. I think I loaded it once to see what it does and never unloaded it. I have had similar crashes (3 or 4 maybe) since I reported this.

Comment 5 Michael Schwendt 2011-05-29 05:47:36 UTC
> for some reason I wasn't added to the CC list and
> missed your comments.

You are the reporter of this ticket. As the reporter, you don't need to be on Cc list, you will receive comments by mail unless you've messed with your bugzilla account's Email Preferences.

Comment 6 Fedora End Of Life 2012-08-16 12:05:58 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.