Bug 442147 - Working with firefox and get a crush very often
Summary: Working with firefox and get a crush very often
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 8
Hardware: All
OS: Linux
low
low
Target Milestone: ---
Assignee: Gecko Maintainer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2008-04-12 02:29 UTC by David Silvano Osollo Orozco
Modified: 2018-04-11 09:57 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2008-10-20 21:29:33 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Working with firefox and get a crush very often (258.67 KB, text/plain)
2008-04-12 02:29 UTC, David Silvano Osollo Orozco
no flags Details

Description David Silvano Osollo Orozco 2008-04-12 02:29:59 UTC
Working with firefox and get a crush very often

Comment 1 David Silvano Osollo Orozco 2008-04-12 02:29:59 UTC
Created attachment 302188 [details]
Working with firefox and get a crush very often

Comment 2 Ville Skyttä 2008-04-12 09:08:31 UTC
This doesn't seem to have anything to do with the zzuf package, moving to firefox.

Comment 3 Matěj Cepl 2008-07-25 15:30:59 UTC
Thanks for the bug report.  We have reviewed the information you have provided
above, and there is some additional information we require that will be helpful
in our diagnosis of this issue.

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.

Comment 4 Matěj Cepl 2008-09-12 14:55:15 UTC
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.

Comment 5 Matěj Cepl 2008-10-20 21:29:33 UTC
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.


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