Closed
Bug 496768
Opened 17 years ago
Closed 15 years ago
"Get all of your tags" on Flickr => 100% CPU usage
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: jk, Unassigned)
Details
(Whiteboard: [CLOSEME 2011-2-25])
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b99) Gecko/20090605 Firefox/3.5b99
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b99) Gecko/20090605 Firefox/3.5b99
When I'm tagging a picture on flickr and let the site display all my existing tags (about 100) via "Get all of my tags", CPU usage instantly goes up to 100%.
Firefox is pretty much unusable in this state until I leave the page.
Reproducible: Always
Steps to Reproduce:
1. Go to one of your pictures on Flickr
2. Click "Add tag"
3. Click "Choose from your tags"
4. Click "get all of your tags" (this puts links to about 100 tags in the page in my case)
Actual Results:
100% CPU usage, Firefox unusable
Expected Results:
low CPU usage
* javascript.options.jit.content=true
* happens in safe-mdoe
| Reporter | ||
Updated•17 years ago
|
Version: unspecified → 3.5 Branch
| Reporter | ||
Comment 1•17 years ago
|
||
Also happens with javascript.options.jit.content=false
Comment 2•15 years ago
|
||
Reporter, are you still seeing this issue with Firefox 3.6.13 or later in safe mode or a fresh profile? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2011-2-25]
Comment 3•15 years ago
|
||
This bug has had the CLOSEME tag for several weeks and the date in the tag is far gone. If the reporter can still see this issue, Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). Then please remove the closeme tag in the whiteboard, mark the bug against the proper version and comment on the bug.
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•