Closed
Bug 359360
Opened 19 years ago
Closed 18 years ago
CPU 100% when uploading a file on Imageshack
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: serge.simon, Unassigned)
Details
Attachments
(1 file)
|
243.14 KB,
image/jpeg
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; fr; rv:1.8.1) Gecko/20061010 Firefox/2.0
I had 8 tabs open, including 2 on Imageshack.us, and I was uploading 2 (very small) files.
The first file has correctly be uploaded, but Firefox hanged on the second imageshack tab. No response anymore from Firefox. Under Windows Taskman, and I saw 100% CPU used by Firefox and I had to kill it.
It's in my opinion a very old bug still there. I already encountered this a lot of time with 1.5* (firefox hang) when writing down messages in forms (for example on bulletin board form reply).
I have a few extensions included :
- adblock plus
- allinone sidebar
- delicious
- dom inspector
- flashgot
- forecastfox
- foxmarks bookmark synchronizer
- free download manager plugin
- get jetable mail
- gmail notifier
- linkchecker
- pdf download
- sage
- viewsourcewith
- web developper
Reproducible: Didn't try
Expected Results:
No hangs !
| Reporter | ||
Comment 1•19 years ago
|
||
Screenshot taken when the problem occured
Comment 2•19 years ago
|
||
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1) Gecko/20061010 Firefox/2.0
Can't reproduce a hang.
Imageshack has usually moving flash ads which can take a lot of CPU time. It is also a very popular site that can take a long time to reach.
Please retest with disabled extensions or in Firefox's safe-mode.
Comment 3•18 years ago
|
||
No response from reporter re: comment 2 -->INCOMPLETE.
Reporter, if you still see this problem with Firefox 2.0.0.4 (or later) please reopen this bug. Thanks!
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → INCOMPLETE
Version: unspecified → 2.0 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•