Bug 1088676

Summary: Fedora 20 Freezes While using Firefox or Chrome
Product: [Fedora] Fedora Reporter: dB <dineshsdb>
Component: xorg-x11-drv-intelAssignee: Adam Jackson <ajax>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 20CC: ajax, dineshsdb, steevithak, xgl-maint
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-20 01:55:25 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
I enclosed Xorg's log file none

Description dB 2014-04-17 01:34:00 UTC 
Description of problem:

I am running Fedora 20 (32-bit)

While using internet in firefox or chrome, my system freezes but mouse and keyboard seems working and I have to reboot my system to start it as normal.

This problem occurs randomly.

Either Adobe flash or intel graphic drivers be the problem??
please guide me to solve this problem ???
Comment 1 dB 2014-04-17 01:56:18 UTC 
Created attachment 887029 [details]
I enclosed Xorg's log file

Please check this log file with respect to my bug

Thanks in advance !!
Comment 2 Steevithak 2014-05-07 18:15:06 UTC 
I'm experiencing a similar problem but only with the latest version of Firefox on Fedora 20. Chrome seems fine. I can run Firefox only if I limit usage to a single tab. If I open a second tab, the entire system become unresponsive. I can switch to a text mode terminal session (Ctrl-Alt-F2) but it takes on the order of five minutes to get a login prompt. If I run top at that point, the system load is upwards of 20 and memory is being allocated at a fantastic rate. Killing the Firefox process usually halts the rapid memory allocation but a full reboot is required afterwards to fully regain responsiveness in the GUI desktop. My work around has been to stop using Firefox and use only Chrome.
Comment 3 dB 2014-05-20 01:55:25 UTC 

*** This bug has been marked as a duplicate of bug 1099070 ***