Bug 705066 - [abrt] evolution-2.32.2-1.fc14: _int_malloc: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-2.32.2-1.fc14: _int_malloc: Process /usr/bin/evolution was k...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a64f6527b46c598f79799dc2aaf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-05-16 14:40 UTC by Sullivan G. Scott, Jr.
Modified: 2012-08-16 14:18 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 14:18:25 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (127.95 KB, text/plain)
2011-05-16 14:40 UTC, Sullivan G. Scott, Jr.
no flags Details

Description Sullivan G. Scott, Jr. 2011-05-16 14:40:54 UTC
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 131017 bytes
cmdline: evolution
component: evolution
Attached file: coredump, 225714176 bytes
crash_function: _int_malloc
executable: /usr/bin/evolution
kernel: 2.6.35.13-91.fc14.x86_64
package: evolution-2.32.2-1.fc14
rating: 4
reason: Process /usr/bin/evolution was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1305556695
uid: 500

How to reproduce
-----
1.Evolution was open and just sitting idle
2. Crash
3.

Comment 1 Sullivan G. Scott, Jr. 2011-05-16 14:40:56 UTC
Created attachment 499176 [details]
File: backtrace

Comment 2 Milan Crha 2011-05-17 05:22:57 UTC
Thanks for a bug report. This seems to be some kind of memory corruption, because this crashed deep in gio/glib and gtk+ code. Is this anyhow reproducible on your machine, please? The thing is that I cannot find from the backtrace what could happen. Reproduce the issue under valgrind may help find out what is going wrong.

Comment 3 Milan Crha 2011-05-17 13:45:20 UTC
Oh, I'm sorry, I forgot to write the valgrind command here, which I usually do, but forgot for some reason. I'm sorry for that. I would use this command:
  $ G_SLICE=always-malloc valgrind --num-callers=50 evolution &>log.txt
The log.txt file will then contain certain data. Note that evolution may not crash when run under valgrind, as valgrind is able to avoid some kind of crashes.

Comment 4 Cyril Sluchanko 2011-05-18 08:37:31 UTC
Package: evolution-2.32.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. App was idle, no user actions. 
2.
3.

Comment 5 Alex Smirnoff 2011-07-13 07:08:12 UTC
Package: evolution-2.32.2-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. woke up notebook from sleep and noticed it crashed
2.
3.

Comment 6 Fedora End Of Life 2012-08-16 14:18:29 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.