Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 505467 - Firefox 3.5 Freezes the entire system, after a random time
Summary: Firefox 3.5 Freezes the entire system, after a random time
Keywords:
Status: CLOSED DUPLICATE of bug 498457
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-ati
Version: 11
Hardware: All
OS: Linux
low
urgent
Target Milestone: ---
Assignee: Dave Airlie
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-12 01:15 UTC by Florent Le Coz
Modified: 2018-04-11 07:33 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-07-02 16:14:13 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
/var/log/dmesg (deleted)
2009-06-13 17:42 UTC, Florent Le Coz 		no flags Details
var/log/Xorg.0.log (deleted)
2009-06-13 17:43 UTC, Florent Le Coz 		no flags Details
/var/log/messages (deleted)
2009-06-13 17:44 UTC, Florent Le Coz 		no flags Details
View All

Description Florent Le Coz 2009-06-12 01:15:00 UTC 
Description of problem:
Firefox, after some random time, just freezes the entire system, and rebooting is the only remaining thing to do.
It never happens with anything else, it's clearly firefox that does this.

Version-Release number of selected component (if applicable):
firefox-3.5-0.20.beta4.fc11.x86_64

How reproducible:
Very often, randomly (can't find out why and when this happens)

Steps to Reproduce:
1. Just run firefox
2. Randomly browse the web
3. freez
Comment 1 Matěj Cepl 2009-06-12 16:25:53 UTC 
When the computer is "frozen", is it really frozen? Aren't you by chance able to press Ctrl+Alt+F2 and get into console? Or if you have some other computer around, wouldn't you be able to connect to your "frozen" computer via ssh? If either of these questions could be answered "yes", could we get /var/log/Xorg.0.log, /var/log/messages, /var/log/dmesg, and (if you have any) /etc/X11/xorg.conf. Could you also take a look at top output to find out which process takes most of the CPU?

Thank you very much.
Comment 2 Florent Le Coz 2009-06-13 17:36:28 UTC 
The sound doesn't stop, only the screen stops to react.
I can't go to an other Console (ctrl+alt+fx), but I can log on the computer with ssh.

(not that it is NOT due to RAM error, because I just changed it, and it still happens)

Here are the asked log files.
Comment 3 Florent Le Coz 2009-06-13 17:42:45 UTC 
Created attachment 347754 [details]
/var/log/dmesg
Comment 4 Florent Le Coz 2009-06-13 17:43:57 UTC 
Created attachment 347755 [details]
var/log/Xorg.0.log

(note that there is no /etc/X11/xorg.conf file)
Comment 5 Florent Le Coz 2009-06-13 17:44:55 UTC 
Created attachment 347756 [details]
/var/log/messages
Comment 6 Florent Le Coz 2009-06-13 17:47:38 UTC 
Also note that this already happened with firefox 3.5beta3 (compiled version from the official website), on Fedora 10.
Comment 7 Florent Le Coz 2009-06-14 22:17:38 UTC 
Oh, and I forgot to look at the top's output.

The process taking 100% of the UC is /usr/bin/Xorg
Comment 8 Matěj Cepl 2009-06-16 22:23:09 UTC 
Blaming Xorg then.
Comment 9 Florent Le Coz 2009-06-27 23:08:19 UTC 
This also happens when I use baobab.
Comment 10 Florent Le Coz 2009-07-02 14:08:50 UTC 
In fact, this happens with many others softwares…

Like compiz fusion, for example.
Is there anything else I could provide to help you find out what's the problem ?...
Comment 11 Matěj Cepl 2009-07-02 16:14:13 UTC 

*** This bug has been marked as a duplicate of bug 498457 ***
Note You need to log in before you can comment on or make changes to this bug.