Bug 161576

Summary: Division by zero in nsFontMetricsPango::CacheFontMetrics
Product: [Fedora] Fedora Reporter: Robin Green <greenrd>
Component: firefoxAssignee: Christopher Aillon <caillon>
Status: CLOSED CURRENTRELEASE QA Contact:
Severity: high Docs Contact:
Priority: medium    
Version: rawhideCC: dm, wtogami
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
URL: http://docs.python.org/ref/yield.html
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2007-04-01 14:53:49 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:
Bug Depends On:    
Bug Blocks: 139531    
Attachments:
Description Flags
Backtrace from gdb none

Description Robin Green 2005-06-24 15:45:28 UTC 
Description of problem:   
Firefox crashes with SIGFPE when visiting 
http://docs.python.org/ref/yield.html , caused by attempt to divide by zero, 
when latest  
gtk2/pango/cairo is installed from rawhide. The zero   
value is in the lineHeight variable in nsFontMetricsPango::CacheFontMetrics. 
Backtrace attached.   
   
Version-Release number of selected component (if applicable):   
firefox-1.0.4-5  
   
How reproducible:   
Always 
   
Steps to Reproduce:   
1. firefox 'http://docs.python.org/ref/yield.html' 
     
Actual results:   
<snip> 
/usr/lib/firefox-1.0.4/run-mozilla.sh: line 159: 14390 Floating point 
exception"$prog" ${1+"$@"} 
   
Expected results:   
No crash 
   
Additional info: 
All latest updates from rawhide installed. 
Workaround: Run firefox with 
MOZ_DISABLE_PANGO=1 firefox
Comment 1 Robin Green 2005-06-24 15:45:28 UTC 
Created attachment 115938 [details]
Backtrace from gdb
Comment 2 Daniel Malmgren 2005-07-20 09:58:16 UTC 
*** Bug 162406 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Clasen 2007-04-01 14:53:49 UTC 
I am pretty sure that this is fixed by now; we are running pango-enabled firefox
by default for a while now, and the cited web page loads fine for me. 

Please reopen if you still see this problem.