Jason Johnston Reporter
	Description • 24 years ago

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; 0.8) Gecko/20010215
BuildID:    2001021508

When an HTML block containing a horizontal rule (<HR>) is set in motion by
incremental positioning, CPU usage gradually rises to 100%, and the time between
steps gradually increases.



Reproducible: Always
Steps to Reproduce:
Set a <div> in motion via JavaScript.  Place a <HR> anywhere inside it.

Actual Results:  Motion gradually slows (time in between positions increases). 
CPU usage grows to 100%.

Removing the horiz. rule eliminates the problem.
If the HR is itself moved in this manner (instead of its containing div), no
slowdown occurs.

This has been reproduced on 3 out of 3 Win2K machines. 

Test pages are at:
http://www.screaminweb.com/mozillatest/slowHR.html 
http://www.screaminweb.com/mozillatest/noHR.html

	HJ
	Comment 1 • 24 years ago

Confirming with build 2001022200 on NT

	Keyser Sose
	Comment 2 • 24 years ago

Marking New as per comments.

	bsharma
	Comment 3 • 24 years ago

qa contact updated.

	bsharma
	Comment 4 • 24 years ago

changing the component to 'Layout'.

	karnaze (gone)
	Comment 5 • 24 years ago

Reassigning to Buster's list.

	karnaze (gone)
	Comment 6 • 24 years ago

Moving to m1.0 and reassigning to waterson.

	basic
	Comment 7 • 23 years ago

still seeing slow down on build 2001102903 win32 trunk
but not really *that* noticable
and CPU does not reach 100% until about half way down the page.

	basic
	Comment 8 • 23 years ago

this seems to be fixed maybe due to the fix in bug 71979 ? Or maybe something else

	basic
	Comment 9 • 23 years ago

forgot to mentioned that I tested with build 2001112104 win32

	Asa Dotzler [:asa]
	Comment 10 • 23 years ago

Bugs targeted at mozilla1.0 without the mozilla1.0 keyword moved to mozilla1.0.1 
(you can query for this string to delete spam or retrieve the list of bugs I've 
moved)

	Alvaro Munoz-Aycuens
	Comment 11 • 23 years ago

WFM on Linux with Build-id:2001113006, the cpu use stays at 0% and it doesn't
deccelerates when scrolling down,just scrolls cleanly.

	Jason Johnston Reporter
	Comment 12 • 23 years ago

Nice!  It works for me now too, Win2K build 2001120208.

Resolving as FIXED.

	Jiri Znamenacek
	Comment 13 • 23 years ago

Sory for the spam, but I'd REALLY like to know what in code caused this change
in last week. It looks unbelievable that one week old Mozilla eated 100% on this
and the new one only about 20%...