Bug 659164 - [abrt] evolution-data-server-2.32.1-1.fc14: magazine_chain_pop_head: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
Summary: [abrt] evolution-data-server-2.32.1-1.fc14: magazine_chain_pop_head: Process ...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
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:b71f5fe3419d4303757fa9efce4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-02 02:02 UTC by António Lima
Modified: 2012-05-12 04:10 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-12-02 12:35:26 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (19.86 KB, text/plain)
2010-12-02 02:02 UTC, António Lima 		no flags Details
View All

Description António Lima 2010-12-02 02:02:41 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/e-addressbook-factory
component: evolution-data-server
crash_function: magazine_chain_pop_head
executable: /usr/libexec/e-addressbook-factory
kernel: 2.6.35.6-48.fc14.i686
package: evolution-data-server-2.32.1-1.fc14
rating: 4
reason: Process /usr/libexec/e-addressbook-factory was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1291254838
uid: 500

How to reproduce
-----
1. Clicked an mailto link and evolution crashed
2.
3.
Comment 1 António Lima 2010-12-02 02:02:44 UTC 
Created attachment 464149 [details]
File: backtrace
Comment 2 Milan Crha 2010-12-02 08:44:41 UTC 
Thanks for a bug report. Is this reproducible, please? I do not see it myself. If it is reproducible, then please close evolution, make sure e-addressbook-factory process is also not running, and then run it on a console like this:
  $ G_SLICE=always-malloc valgrind --num-callers=50 /usr/libexec/e-addressbook-factory &>eaf.log

and then run evolution on another console, and try to reproduce the crash. If it doesn't crash then close evolution and wait for 10 seconds till the factory is closed automatically, or just close it with Ctrl+C in it's terminal, if it'll take more than 10 seconds (it'll also take some time until valgrind is done with all the memory checking on close, so you might see whether it does anything with the processor usage.

When it's done, please upload the eaf.log, maybe it'll show something. Thanks in advance.
Comment 3 António Lima 2010-12-02 11:52:13 UTC 
Hi,

I can't seem to reproduce the bug. Yesterday it crashed twice straight but maybe I should have tested further before reporting.

I think you may close the bug, if it happens again and I can reproduce it I'll reopen the bug and attach the information you requested.

Thanks and sorry for the trouble.
Comment 4 Milan Crha 2010-12-02 12:35:26 UTC 
Thanks for the update. I'm closing this then, but it's pity you cannot reproduce it right now. And do not worry, there is no trouble with this at all :)
Comment 5 Mikhail 2012-05-12 04:10:19 UTC 
This problem also occurs with me, but i couldn't report via abrt because this report exists



--- Running report_Bugzilla ---
Logging into Bugzilla at https://bugzilla.redhat.com
Bug is already reported: 659164
Logging out
Status: CLOSED INSUFFICIENT_DATA https://bugzilla.redhat.com/show_bug.cgi?id=659164
Note You need to log in before you can comment on or make changes to this bug.