Bug 1040090

Summary: [abrt] firefox-25.0-3.fc20: magazine_chain_pop_head: Process /usr/lib64/firefox/firefox was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: mswal28462 <mswal2846>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED WORKSFORME QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: altbinspam, danielsun3164, ezwen-redhatbugzilla, fedora, gecko-bugs-nobody, igor.redhat, naval.antennas, w.isaac.cortes
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/51d8b5bb144cf15aaa8e9a8e4e3b87e4a82c3b7d
Whiteboard: abrt_hash:e3869ccc9f3b2791e32d88c38c7c4126fcdcbda8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-11 17:12:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description mswal28462 2013-12-10 17:07:02 UTC 
Version-Release number of selected component:
firefox-25.0-3.fc20

Additional info:
reporter:       libreport-2.1.9
backtrace_rating: 4
cmdline:        /usr/lib64/firefox/firefox https://blueharmony.bhprod.ibm.com:9443/uaweb/rational/APPROVE?sid=CLEAR_QUEST&stage=1&passcode=74307670-p816-0
crash_function: magazine_chain_pop_head
executable:     /usr/lib64/firefox/firefox
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 magazine_chain_pop_head at gslice.c:545
 #1 thread_memory_magazine1_alloc at gslice.c:848
 #2 g_slice_alloc at gslice.c:1007
 #3 emit_in_idle at gfilemonitor.c:414
 #4 g_file_monitor_emit_event at gfilemonitor.c:720
 #5 ih_event_callback at inotify-helper.c:196
 #6 ip_event_dispatch at inotify-path.c:493
 #7 ip_event_callback at inotify-path.c:629
 #8 ik_process_eq_callback at inotify-kernel.c:579
 #13 g_main_context_iteration at gmain.c:3774
Comment 1 mswal28462 2013-12-10 17:07:10 UTC 
Created attachment 834860 [details]
File: backtrace
Comment 2 mswal28462 2013-12-10 17:07:11 UTC 
Created attachment 834861 [details]
File: cgroup
Comment 3 mswal28462 2013-12-10 17:07:13 UTC 
Created attachment 834862 [details]
File: core_backtrace
Comment 4 mswal28462 2013-12-10 17:07:15 UTC 
Created attachment 834863 [details]
File: dso_list
Comment 5 mswal28462 2013-12-10 17:07:16 UTC 
Created attachment 834864 [details]
File: environ
Comment 6 mswal28462 2013-12-10 17:07:20 UTC 
Created attachment 834865 [details]
File: limits
Comment 7 mswal28462 2013-12-10 17:07:21 UTC 
Created attachment 834866 [details]
File: maps
Comment 8 mswal28462 2013-12-10 17:07:23 UTC 
Created attachment 834867 [details]
File: open_fds
Comment 9 mswal28462 2013-12-10 17:07:27 UTC 
Created attachment 834868 [details]
File: proc_pid_status
Comment 10 mswal28462 2013-12-10 17:07:28 UTC 
Created attachment 834869 [details]
File: var_log_messages
Comment 11 Martin Stransky 2013-12-11 17:12:18 UTC 
This is an automatic bug processing. If you can reproduce the crash (or see it regularly) please reopen the bug and remove [abrt] from the subject. Thanks!
Comment 12 igor.redhat@gmail.com 2014-03-03 19:44:47 UTC 
I can't say I can reproduce this at will but I do get this crash regularly, i.e., a few times per week. I'd love to reopen this and remove [abrt] from the subject but it doesn't sound like I have permissions to do anything other than adding a comment on this bug...
Comment 13 Christian Stadelmann 2014-06-25 09:39:38 UTC 
I ran into this bug right now running FF30 on F20 with a relatively fresh profile (ca. 2 months old, no history/cookies/…).
Comment 14 Lacrocivious Acrophosist 2014-06-26 13:52:13 UTC 
This is the first time I have had the temerity to reopen a closed bug, but whatever this is, it isn't fixed and it is getting worse, on a Fedora 20 new install and fresh profile only a few weeks old.