User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021029 Phoenix/0.4 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021029 Phoenix/0.4 when i first go to a site and it loads, the entire page is displayed then suddenly i go to 100% cpu usage for 10-20seconds. during this time none of the animated banners (either flash or ani .gifs) are animated. since i'm on a dual proc system i can use other programs just fine but phoenix won't respond until it finishes whatever processing it is doing. once it finished nothing visually changes on the page i'm viewing except that the animated ads start going. tvguide.com has been particularly bad for me with this happening but i've also seen it on fark.com, hardforum.com and several online news sites. the only common factor i can think of is the animated banners and ads. Reproducible: Sometimes Steps to Reproduce: 1. try going to any site that is heavy with animated ads and banners. 2. 3. Actual Results: cpu will go to 100% for 10-20 seconds then drop back to normal usage. Expected Results: loaded the site and been immediately usable i'm using the pinball theme but i've had this problem since version .2 with the default skin.

Does this only happen with Phoenix, or do you see it in Mozilla also? Did you install Phoenix into a clean directory (not overwriting an old installation) and create a new profile?

How about a test case?

Jonathan, without a testcase or URL to confirm this bug it's not going to be fixed. Please report back to the bug and add a comment pointing to a demonstration of the problem.

This sounds an awful lot like bug 94828, it's cropped up again and is getting a few bug reports here and there.

In other words, it's a duplicate of bug 94828, typing up bug replies when tired isn't a good idea.

Checked both http://www.tvguide.com and http://www.fark.com sites using Gecko/20021216 Phoenix/0.5 on Windows NT 4.0 and found no problems: tvguide.com was finished loading in less than a second and also fark.com was done very fast. Jonathan, do you still encounter the problems reported? Did you check it with the newest build available? Nevertheless it really sounds like a dupe of bug #86319 so if problem still persists I'd suggest to duplicate it...

Nothing happened since nearly 2 month so I will mark this one duplicate of bug #86319. I choose bug #86319 since bug #94828 might get marked dup., too of bug #86319. *** This bug has been marked as a duplicate of 86319 ***

v.