Closed Bug 559004 Opened 15 years ago Closed 13 years ago

Firefox constantly freezes and becomes unresponsive on facebook chat.

Categories

(Firefox :: General, defect)

3.6 Branch
x86
Windows 7
defect
Not set
major

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: siger, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-GB; rv:1.9.2.3) Gecko/20100401 Firefox/3.6.3 (.NET CLR 3.5.30729) Click to see which of your contacts are online(facebook) then firefox freezes and therefore needs to restart otherwise takes several minutes to respond. Usually happens when you click on the bottom right-hand corner to show online contacts. Reproducible: Always Steps to Reproduce: 1.On firefox click contacts on bottom right hand corner 2.while the pop up window for contacts is open, navigate to another page on facebook 3.If another tab is open firefox will freeze completely Actual Results: same freezing again and again Expected Results: it should have allowed me to open other pages and not freeze everything
Safari seemed to have similar issues last time I checked but IE8 worked fine.
What version of quicktime, flash and java do you have, and does this happen in safe mode? http://support.mozilla.com/kb/Safe+mode
Severity: critical → major
Version: unspecified → 3.6 Branch
Quicktime 7.6.6 ...Java v.6 u.18 ...Adobe Flash Player version 10.0.45.2
Yes this happens in safe mode as well.
I was able to reproduce this as well until Firefox 4, when it seemed to be fixed. Can you still reproduce this bug in Firefox 6? Please update to Firefox 6 or later, update your plugins, and retest in a new profile. If you still see the issue with the updated version of Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME. http://getfirefox.com/
siger doesn't respond, so WFM per comment 5
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.