Description of problem: Firefox crash with following error message: -------- /usr/lib/firefox-3.0.4/run-mozilla.sh: line 131: 6654 浮点数例外 "$prog" ${1+"$@"} ------- Version-Release number of selected component (if applicable): firefox-3.0.4-1.el5-ia64 How reproducible: not always, but quite often Possible Steps to Reproduce: 1. firefox -createprofile, open some webpages with different tabs, and close firefox with multiple tabs 2. firefox -safe-mode, select all options, click "save changes and restart" 3. in the popup window, click "restore ..." 4. sometimes, I only create a profile and then start safe-mode, it will crash. Actual results: Expected results: Additional info:
This message itself doesn't mean much -- firefox generates with every other crash. First of all, could we get output of the command rpm -qa *xulrun* *firefox* *mozilla* *flash* *plugin* Please also install firefox-debuginfo (debuginfo-install is from yum-utils package). debuginfo-install firefox Then run firefox with a parameter -g. That will start firefox running inside of gdb debugger. Then use command run and do whatever you did to make firefox crash. When it happens, you should go back to the gdb and run (gdb) thread apply all backtrace This produces usually many screens of the text. Copy all of them into a text editor and attach the file to the bug as an uncompressed attachment. We will review this issue again once you've had a chance to attach this information. Thanks in advance.
Reporter, could you please reply to the previous question? If you won't reply in one month, I will have to close this bug as INSUFFICIENT_DATA. Thank you.
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as INSUFFICIENT_DATA.