Fireworks DHTML causes 100% CPU usage

RESOLVED INCOMPLETE

Status

()

RESOLVED INCOMPLETE
13 years ago
9 years ago

People

(Reporter: wasilkov, Unassigned)

Tracking

1.5.0.x Branch
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(URL)

(Reporter)

Description

13 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

broken web site computerra.ru

Reproducible: Always




dial-up connection
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9a1) Gecko/20060109 Firefox/1.6a1 ID:2006010921

Some ads on that site are causing a 100% CPU usage.
With an ad blocking extension like Adblock Plus you could decrease that.
I see no other problems at first sight.

Comment 2

13 years ago
It's this DHTML page (fireworks) that is causing the 100% CPU usage:
http://ad.valuehost.ru/cgi-bin/adcycle.cgi?gid=13&t=_top&id=173&type=iframe

I couldn't even save the page to attach it here, which is probably needs to be done, since there's a non-zero chance that URL goes offline soon.
Summary: no scrolling, freezing, high mem and CPU usage at all tabs: broken web site? → Fireworks DHTML causes 100% CPU usage

Updated

12 years ago
Version: unspecified → 1.5.0.x Branch
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME
http://www.mozilla.com
http://support.mozilla.com/kb/Managing+profiles
http://support.mozilla.com/kb/Safe+mode
No reply, INCOMPLETE. Please retest with Firefox 3.6.3 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.