Bug 652256 - [abrt] evolution-data-server-2.32.0-3.fc14: malloc_consolidate: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.0-3.fc14: malloc_consolidate: Process /usr/...
Keywords:
Status: CLOSED DUPLICATE of bug 658483
Alias: None
Product: Fedora
Classification: Fedora
Component: evolution-data-server
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Matthew Barnes
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:8d3a2c8448a6865341803ccf42f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-11 13:33 UTC by BartS
Modified: 2012-03-30 12:36 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:36:22 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (39.64 KB, text/plain)
2010-11-11 13:33 UTC, BartS
no flags Details

Description BartS 2010-11-11 13:33:55 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
comment: random crash
component: evolution-data-server
crash_function: malloc_consolidate
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.6-48.fc14.i686
package: evolution-data-server-2.32.0-3.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1289482402
uid: 500

Comment 1 BartS 2010-11-11 13:33:58 UTC
Created attachment 459757 [details]
File: backtrace

Comment 2 BartS 2010-11-11 21:06:58 UTC
Package: evolution-data-server-2.32.0-3.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


Comment
-----
random crash

Comment 3 Milan Crha 2010-11-12 08:50:31 UTC
Thanks for a bug report. This seems to happen with a libxml library, when it is trying to parse an ESource, an XML description of it. As that all is done in the main thread, and other two threads are not doing anything special, then I've not much idea what may happen.

Are you able to reproduce this consistently? You said in the previous comment that it's a "random crash", thus I suppose you are not able to reproduce it? Though that second comment confuses me, as it means it happened to you twice?

Comment 4 abrt-bot 2012-03-30 12:36:22 UTC
Backtrace analysis found this bug to be similar to bug #658483, closing as duplicate.

This comment is automatically generated.

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


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