Bug 675110

Summary: Firefox crashes when allow_execmem is off
Product: [Fedora] Fedora Reporter: Luis Cruz <marvao2010>
Component: firefoxAssignee: Gecko Maintainer <gecko-bugs-nobody>
Status: CLOSED UPSTREAM QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 14CC: gecko-bugs-nobody, mads, mcepl
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-07-21 22:35:51 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
Selinux booleans and logs, and CLI logs when I run firefox none

Description Luis Cruz 2011-02-04 10:56:55 UTC
Created attachment 476972 [details]
Selinux booleans and logs, and CLI logs when I run firefox

Description of problem:

In a clean installation of Fedora 14 with all updates (2011-Feb-04) applied and without any external software added, if selinux boolean allow_execmem is set to off, firefox crashes immediately.

If I disable every firefox extension manually, firefox still crashes. However, if I run firefox in safe mode, firefox runs normally.

Please find attached the selinux troubleshooter log. I also include the current state of all selinux booleans and the output I get when I run firefox from the command line.


Version-Release number of selected component (if applicable):

firefox-3.6.13-1.fc14.i686

How reproducible:

Always


Steps to Reproduce:
1. Turn off allow_execmem
2. Run firefox
3.
  
Actual results:


Expected results:


Additional info:

Comment 1 Luis Cruz 2011-02-22 23:46:39 UTC
Apparently, the JIT component needs execmem privileges, because if I set the two options below to "false" (by using address "about:config" in the URL field), firefox runs without any problems.
 
javascript.options.jit.chrome
javascript.options.jit.contentfalse

Comment 2 Matěj Cepl 2011-07-21 22:35:51 UTC
There is an epic bug for this at the upstream bug database (https://bugzilla.mozilla.org/show_bug.cgi?id=506693) and we believe that it is more appropriate to let it be resolved upstream.

We will continue to track (and try to fix) the issue in the centralized upstream bug tracker, and will review any bug fixes that become available for consideration in future updates.

We would strongly encourage you to subscribe to the upstream bug as well (by logging in and adding yourself to the Cc list), so that you can provide whatever information required for the successful resolving of this issue.

Thank you for helping to make free software better.