Closed Bug 212278 Opened 22 years ago Closed 21 years ago

sswug.org - the task manager reports 100% cpu usage

Categories

(Tech Evangelism Graveyard :: English US, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: davito9fr, Unassigned)

References

()

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 just open the page then scroll up and down a few times. Each time, the cpu usage climbs until it reaches 100% (almost all devoted to Mozilla). I did the test on a XP Pro laptop with the same results. Reproducible: Always Steps to Reproduce: 1.load the page 2.scroll up and down 3.watch the cpu usage Actual Results: cpu usage went to 100% Expected Results: kept it's usual low profile!
wfm using build 2003070308 (trunk) on Win2k. CPU remains at 10%.
I downloaded Mozilla 1.5a 20030709. Same results on the W2K system. I didn't want to install the version on my laptop just now. I did extensive tests: upon page load, Mozilla cpu usage is 0% (fine) drag the scroll bar completely to the bottom and back to the top: after a few seconds, Mozilla's cpu usage "stabilizes" between 8 and 19% second down-up: cpu between 17 and 33% third down-up: cpu between 31 and 47% fourth down-up: cpu between 64 and 77% fifth down-up: cpu at 99% I didn't try to go further! I did tests with more than one tab. Just closing the tab on the sswug website brings Mozilla's cpu usage back to 0. One thing that could influence the problem: both the W2K system and the XP Pro system access to the Internet through the same LAN. I will try this evening using my modem at home. I did the same test using MSIE on the W2K system and Opera on the XP Pro laptop: I didn't find anything abnormal.
I checked the base address http://www.sswug.org/ and I got the same behaviour, except that I needed a little more scrollbar down-ups to reach 100%
The problem appears only if you scroll using the mouse and the scroll bar, not if you scroll with the keyboard (using page up and page down or up arrow and down arrow).
Looking at the sourcecode I found they check only for ns4 browers, so netscape 4.x gets nsmenu.js, all others get iemenu.js. The javascript console confirmed with tons of warnings and errormessages, see below. So I assume it´s a matter of Tech Evangelism. Warning: reference to undefined property document.layers Source File: http://www.sswug.org/searchresults.asp?keywordstofind=random%20number Line: 195 Warning: deprecated with statement usage Source File: http://www.sswug.org/menus/iemenu.js Line: 1, Column: 146 Source Code: nt(s.style.top)+bw+"px";if(SM) with(mc.style){mc.cwidth=width;mc.cheight=height;width=parseInt(width)+2*bw+"px";height=parseInt(height)+2*bw+"px";}}}else{mc.s.style.top=mc.stop;mc.s.style.left=mc.sleft;if(SM){mc.style.width=mc.cwidth;mc.style.height=mc.ch Warning: function GetLeftTop does not always return a value Source File: http://www.sswug.org/menus/iemenu.js Line: 1, Column: 49 Source Code: Top];if(NS) return [f.pageXOffset,f.pageYOffset];}function GetWidthHeight(f){if(!f) f=mFrame;if(NS||SM){var k=(OP||KQ?0:f.scrollbars.visible?20:0);return [f.innerWidth-k,f.innerHeight-k];}else return [GetBodyObj(f).clientWidth,GetBodyObj(f).clientHeight]; Warning: reference to undefined property dmbtbF[t] Source File: http://www.sswug.org/menus/iemenu.js Line: 1
Assignee: general → english-us
Component: Browser-General → English US
Product: Browser → Tech Evangelism
QA Contact: general → english-us
Version: Trunk → unspecified
Summary: the task manager reports 100% cpu usage → sswug.org - the task manager reports 100% cpu usage
seems to work fine for me with a fast machine and a recent trunk build. please reopen if you can reproduce.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
ok, with Mozilla 1.7.3, but on the same XP Pro laptop, everything works fine.
Product: Tech Evangelism → Tech Evangelism Graveyard
You need to log in before you can comment on or make changes to this bug.