Bug 161576 - Division by zero in nsFontMetricsPango::CacheFontMetrics
Division by zero in nsFontMetricsPango::CacheFontMetrics
Product: Fedora
Classification: Fedora
Component: firefox (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Christopher Aillon
: 162406 (view as bug list)
Depends On:
  Show dependency treegraph
Reported: 2005-06-24 11:45 EDT by Robin Green
Modified: 2007-11-30 17:11 EST (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2007-04-01 10:53:49 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
Backtrace from gdb (9.21 KB, text/plain)
2005-06-24 11:45 EDT, Robin Green
no flags Details

  None (edit)
Description Robin Green 2005-06-24 11:45:28 EDT
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):   
How reproducible:   
Steps to Reproduce:   
1. firefox 'http://docs.python.org/ref/yield.html' 
Actual results:   
/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 
Comment 1 Robin Green 2005-06-24 11:45:28 EDT
Created attachment 115938 [details]
Backtrace from gdb
Comment 2 Daniel Malmgren 2005-07-20 05:58:16 EDT
*** Bug 162406 has been marked as a duplicate of this bug. ***
Comment 3 Matthias Clasen 2007-04-01 10:53:49 EDT
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.

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