Bug 675110 - Firefox crashes when allow_execmem is off
Summary: Firefox crashes when allow_execmem is off
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 14
Hardware: i686
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-04 10:56 UTC by Luis Cruz
Modified: 2018-04-11 10:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-21 22:35:51 UTC
Type: ---


Attachments (Terms of Use)
Selinux booleans and logs, and CLI logs when I run firefox (8.83 KB, text/plain)
2011-02-04 10:56 UTC, Luis Cruz
no flags Details


Links
System ID Private Priority Status Summary Last Updated
Mozilla Foundation 506693 0 None None None Never

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.


Note You need to log in before you can comment on or make changes to this bug.