Bug 1045788

Summary: firefox: syscall(): firefox killed by SIGSEGV
Product: [Fedora] Fedora Reporter: mdmpsyd <mdmpsyd>
Component: firefoxAssignee: Martin Stransky <stransky>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: aleksey, altbinspam, austinenglish, bignikita, brandon.egbert, b, burning, charles_rose, collura, daramas444, diego.ml, error, fedora, finid, gecko-bugs-nobody, germano.massullo, hancockrwd, hlx98007, holmja, hsing, hugh, igor.redhat, ilmostro7, info, iweiss, jdmf42, juha.heljoranta, klaus, lr_mau, mdmpsyd, michael.faille, mj.wilson.uk, mogzilla, neteler, ravishankar, req1348, rhack, samtygier, sara.c, sayak.bugsmith, scattol, stransky, syswwz, tech, thenscheid, unluckyrogue, utku, webdesigner
Target Milestone: ---Flags: stransky: needinfo?
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/1165a361da284e6d669fb0b480d840b6f99ca321
Whiteboard: abrt_hash:9d8749fd115842166e89051aebf182b5128c44db
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-30 00:47:33 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
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 mdmpsyd@gmail.com 2013-12-22 00:36:08 UTC
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

Comment 1 mdmpsyd@gmail.com 2013-12-22 00:36:13 UTC
Created attachment 840216 [details]
File: backtrace

Comment 2 mdmpsyd@gmail.com 2013-12-22 00:36:15 UTC
Created attachment 840217 [details]
File: cgroup

Comment 3 mdmpsyd@gmail.com 2013-12-22 00:36:17 UTC
Created attachment 840218 [details]
File: core_backtrace

Comment 4 mdmpsyd@gmail.com 2013-12-22 00:36:19 UTC
Created attachment 840219 [details]
File: dso_list

Comment 5 mdmpsyd@gmail.com 2013-12-22 00:36:20 UTC
Created attachment 840220 [details]
File: environ

Comment 6 mdmpsyd@gmail.com 2013-12-22 00:36:22 UTC
Created attachment 840221 [details]
File: limits

Comment 7 mdmpsyd@gmail.com 2013-12-22 00:36:25 UTC
Created attachment 840222 [details]
File: maps

Comment 8 mdmpsyd@gmail.com 2013-12-22 00:36:27 UTC
Created attachment 840223 [details]
File: open_fds

Comment 9 mdmpsyd@gmail.com 2013-12-22 00:36:28 UTC
Created attachment 840224 [details]
File: proc_pid_status

Comment 10 mdmpsyd@gmail.com 2013-12-22 00:36:30 UTC
Created attachment 840225 [details]
File: var_log_messages

Comment 11 Matthew Wilson 2014-01-04 13:02:54 UTC
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

Comment 12 ILMostro 2014-01-04 21:56:58 UTC
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.

Comment 13 ILMostro 2014-01-04 22:00:08 UTC
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

Comment 14 Martin Stransky 2014-01-06 12:56:42 UTC
This is an automated bug update. If you can reproduce the bug, please reopen and remove the [abrt] string from subject.

Thanks!

Comment 15 Matthew Wilson 2014-01-07 11:20:32 UTC
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.

Comment 16 brandon.egbert 2014-01-13 16:49:21 UTC
I'm getting this every time I try to launch Firefox.

Comment 17 Benjamin 2014-02-02 11:08:59 UTC
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

Comment 18 scattol 2014-02-02 13:21:02 UTC
still happens regularly making firefox essentially unusable

Comment 19 collura 2014-02-11 05:54:10 UTC
still happens as of

  firefox-27.0-1.fc20.x86_64
  kernel-3.12.9-301.fc20.x86_64

Comment 20 Mauricio 2014-02-20 19:18:08 UTC
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

Comment 21 Christian Stadelmann 2014-03-25 23:17:48 UTC
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

Comment 22 Michael Hampton 2014-04-14 05:00:37 UTC
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.

Comment 23 Diego 2014-04-17 07:36:05 UTC
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

Comment 24 daramas444 2014-04-18 06:55:18 UTC
[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.

Comment 25 Diego 2014-04-18 07:02:17 UTC
(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.

Comment 26 hlx98007 2014-04-18 12:00:57 UTC
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.

Comment 27 Martin Stransky 2014-04-18 15:01:54 UTC
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

Comment 28 KitchM 2014-04-18 16:46:26 UTC
Is ABRT not working on the system?

Comment 29 Ted Henscheid 2014-04-19 01:27:44 UTC
Yes ABRT is running on the system.  That was how I reported the issue.

Comment 30 KitchM 2014-04-19 03:13:27 UTC
Then I wonder why a backtrace is requested.  That's what ABRT generates.

Comment 31 daramas444 2014-04-19 09:14:36 UTC
(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

Comment 32 Dario Castellarin 2014-04-20 22:29:55 UTC
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

Comment 33 burning 2014-04-28 06:16:15 UTC
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

Comment 34 hlx98007 2015-02-26 15:02:03 UTC
Looks like this problem is not more with new new FF/flash versions.

Fedora 21 doesn't have this problem.

Comment 35 Fedora End Of Life 2015-05-29 10:06:10 UTC
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.

Comment 36 Fedora End Of Life 2015-06-30 00:47:33 UTC
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.