Closed Bug 585380 Opened 14 years ago Closed 13 years ago

Freeze of Firefox

Categories

(Firefox :: General, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: jyv110, Unassigned)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b2) Gecko/20100720 Firefox/4.0b2
Build Identifier: Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b2) Gecko/20100720 Firefox/4.0b2

most of the system is under freeze,
seems like the plugin container is 100% CPU
it requires to shutdown the process plugincontainer

Reproducible: Always

Steps to Reproduce:
1.http://www.raffles.com
2.observe freeze
3.
Actual Results:  
freeze

Expected Results:  
system not frozen

workaround: do not surf on http://www.raffles.com
Group: core-security
(In reply to comment #0)
> User-Agent:       Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b2)
> Gecko/20100720 Firefox/4.0b2
> Build Identifier: Mozilla/5.0 (Windows; Windows NT 5.1; rv:2.0b2)
> Gecko/20100720 Firefox/4.0b2
> 
> most of the system is under freeze,
> seems like the plugin container is 100% CPU
> it requires to shutdown the process plugincontainer
> 
> Reproducible: Always
> 
> Steps to Reproduce:
> 1.http://www.raffles.com
> 2.observe freeze
> 3.
> Actual Results:  
> freeze
> 
> Expected Results:  
> system not frozen
> 
> workaround: do not surf on http://www.raffles.com

site works now
status for me: filled
Upgraded to Firefox 4.  At a website, after clicking the second button, everything freezes.  Same result using FF 3.  I thought it was a virus, so I ran a Norton virus scan, it indicated it was running but it never completed the scan.  I am using XP.  By the way, If someone tries to get 'Support' and forgets their user name, there is no way of recovering it (I tried for too long).  I removed Firefox 3 & 4, problem cured.  Re-installed FF 3, everything good to go.
Version: unspecified → Trunk
closing based on comment 1
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.