Version-Release number of selected component: firefox-26.0-3.fc20 Additional info: reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.11.10-300.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 33 (9 frames) #0 syscall at ../sysdeps/unix/sysv/linux/x86_64/syscall.S:38 #1 epoll_wait at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/third_party/libevent/epoll_sub.c:51 #2 epoll_dispatch at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/third_party/libevent/epoll.c:407 #3 event_base_loop at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/third_party/libevent/event.c:1607 #4 base::MessagePumpLibevent::Run at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/base/message_pump_libevent.cc:340 #5 RunHandler at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/base/message_loop.cc:213 #6 MessageLoop::Run at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/base/message_loop.cc:187 #7 base::Thread::ThreadMain at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/base/thread.cc:160 #8 ThreadFunc at /usr/src/debug/xulrunner-26.0/mozilla-release/ipc/chromium/src/base/platform_thread_posix.cc:39 Potential duplicate: bug 1045599
Created attachment 840216 [details] File: backtrace
Created attachment 840217 [details] File: cgroup
Created attachment 840218 [details] File: core_backtrace
Created attachment 840219 [details] File: dso_list
Created attachment 840220 [details] File: environ
Created attachment 840221 [details] File: limits
Created attachment 840222 [details] File: maps
Created attachment 840223 [details] File: open_fds
Created attachment 840224 [details] File: proc_pid_status
Created attachment 840225 [details] File: var_log_messages
Another user experienced a similar problem: Occurred on close of Firefox after normal browsing session. No plugins installed. firefox-26.0-3.fc20.x86_64 xulrunner-26.0-2.fc20.x86_64 reporter: libreport-2.1.10 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.12.5-302.fc20.x86_64 package: firefox-26.0-3.fc20 reason: firefox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
same here, and I continue to experience these problems xulrunner-26.0-1.fc19.x86_64 firefox-26.0-2.fc19.x86_64 Are they supposed to have the same version/release numbers? Or should xulrunner be uninstalled if it comes "bundled" with the firefox package? I'm not sure about that.
I have to mention that I do have a "local" version of Aurora in my Home directory, if other cases have the same issue as well as a local Aurora release, it might be worth looking into that as a possible conflict; otherwise, it has nothing to do with it. :p
This is an automated bug update. If you can reproduce the bug, please reopen and remove the [abrt] string from subject. Thanks!
Crash occurs for me most times I close Firefox, whether browsing for a short or long period of time. I have no plugins installed. See also bug #1048552, which happens to me when using a VM.
I'm getting this every time I try to launch Firefox.
Another user experienced a similar problem: "random" crash, browser was not even in foreground reporter: libreport-2.1.11 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.12.8-300.fc20.x86_64 package: firefox-26.0-6.fc20 reason: firefox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
still happens regularly making firefox essentially unusable
still happens as of firefox-27.0-1.fc20.x86_64 kernel-3.12.9-301.fc20.x86_64
Another user experienced a similar problem: killed after the confirm install complements prompt was showing reporter: libreport-2.1.12 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.13.3-201.fc20.x86_64 package: firefox-27.0-1.fc20 reason: firefox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: This crash happened on starting Firefox right after 1045788 happened (separate restart). Those two bugs might be related. This bug never occured to me before. reporter: libreport-2.2.0 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.13.6-200.fc20.x86_64 package: firefox-28.0-3.fc20 reason: firefox killed by SIGSEGV runlevel: N 3 type: CCpp uid: 1000
This occurred to me at exit using firefox-28.0-3.fc20.x86_64 kernel-3.13.9-200.fc20.x86_64 It doesn't appear to be easily reproducible.
Hi guys, I think I've found an easy way to reproduce the problem: run firefox with trickle, and the crash I almost certain! For example: trickle -s -d 2000 -u 180 firefox Can anybody test and see if that triggers the bug? Bests, Diego
[edouard@EDStation]~% trickle -s -d 2000 -u 180 firefox (process:6031): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed firefox does launch up and is running flawlessly though. Fedora 20 up to date, x86_64.
(In reply to daramas444 from comment #24) > [edouard@EDStation]~% trickle -s -d 2000 -u 180 firefox > (process:6031): GLib-CRITICAL **: g_slice_set_config: assertion > 'sys_page_size == 0' failed > > firefox does launch up and is running flawlessly though. > > Fedora 20 up to date, x86_64. Try opening "www.speedtest.net". It always crashes for me in that situation.
It might be a flash plugin problem. Firefox used to crash everytime I visit a website with flash element. Re-install the flash-plugin from ADOBE didn't work, deleting personal files did not work. Don't know why. Strangely when I re-install Fedora 20, the problem is no more.
Can you please attach a backtrace of the crash? (If you still see it). How-to is at http://fedoraproject.org/wiki/Debugging_guidelines_for_Mozilla_products#Application_crash
Is ABRT not working on the system?
Yes ABRT is running on the system. That was how I reported the issue.
Then I wonder why a backtrace is requested. That's what ABRT generates.
(In reply to Diego from comment #25) > Try opening "www.speedtest.net". It always crashes for me in that situation. not on my machine, either using firefox or the command line you suggested
Another user experienced a similar problem: Not sure, I was reading a page o Slashdot when firefox locked up and crashed a few seconds later. reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.13.10-200.fc20.x86_64 package: firefox-28.0-3.fc20 reason: firefox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Another user experienced a similar problem: crashed upon loading the javascript part of http://www.heise.de/extras/netwars/ reporter: libreport-2.2.1 backtrace_rating: 4 cmdline: /usr/lib64/firefox/firefox crash_function: syscall executable: /usr/lib64/firefox/firefox kernel: 3.13.10-200.fc20.x86_64 package: firefox-28.0-3.fc20 reason: firefox killed by SIGSEGV runlevel: N 5 type: CCpp uid: 1000
Looks like this problem is not more with new new FF/flash versions. Fedora 21 doesn't have this problem.
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 20 is 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 change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. 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.
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.