Bug 725011 - firefox 5.0 segfaults on IA64
Summary: firefox 5.0 segfaults on IA64
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: firefox
Version: 5.7
Hardware: ia64
OS: Linux
unspecified
urgent
Target Milestone: rc
: ---
Assignee: Red Hat Gecko Maintainer
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-22 15:03 UTC by Aleš Mareček
Modified: 2012-06-11 10:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-06-11 10:17:41 UTC
Target Upstream Version:

Attachments (Terms of Use)
Firefox strace log (219.68 KB, text/plain)
2011-07-22 15:03 UTC, Aleš Mareček 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)


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

Description Aleš Mareček 2011-07-22 15:03:45 UTC 
Created attachment 514719 [details]
Firefox strace log

Description of problem:
I pick machine from Beaker and installed Firefox 5 in there. Firefox wasn't able to start and was killed by SIGSEGV.

Version-Release number of selected component (if applicable):
firefox-5.0-1.el5
xulrunner-5.0-1.el5

How reproducible:
Always

Steps to Reproduce:
1. Install RHEL-5.7 machine with Firefox 5 on IA64 architecture
2. Run X and try to run Firefox
  
Actual results:
Segfaults

Expected results:
Run properly, no segfaults.

Additional info:
Firefox 3 works properly.
Comment 1 Tomas Pelka 2011-08-03 09:29:05 UTC 
Just note that same issue is on RHEL4.
Comment 2 RHEL Program Management 2012-01-09 14:36:08 UTC 
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.8 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.
Comment 3 Martin Stransky 2012-06-11 10:17:41 UTC 
Already fixed.
Note You need to log in before you can comment on or make changes to this bug.