Hide Forgot
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
Created attachment 834860 [details] File: backtrace
Created attachment 834861 [details] File: cgroup
Created attachment 834862 [details] File: core_backtrace
Created attachment 834863 [details] File: dso_list
Created attachment 834864 [details] File: environ
Created attachment 834865 [details] File: limits
Created attachment 834866 [details] File: maps
Created attachment 834867 [details] File: open_fds
Created attachment 834868 [details] File: proc_pid_status
Created attachment 834869 [details] File: var_log_messages
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!
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...
I ran into this bug right now running FF30 on F20 with a relatively fresh profile (ca. 2 months old, no history/cookies/…).
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.