Closed
Bug 116363
Opened 24 years ago
Closed 24 years ago
poor scrolling performance on moderately sized document
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: darin.moz, Assigned: attinasi)
References
()
Details
(Keywords: perf)
i was browsing the toc for the HTML4.01 spec and noticed that scrolling
performance is surprisingly slow relative to other pages of similar size.
i'm not aware of existing layout bugs that might explain poor performance
on this particular page, so i figure filing this bug might be worthwhile.
it seems to be the nested lists that cause the slowdown. on my 850Mhz 256Mb
machine scrolling over the nested lists pegs the cpu hard.
Comment 1•24 years ago
|
||
wfm (build 20011220 06), i'm not seeing any degradation of performance,
scrolling with both keyboard and mouse, and using the arrows.
however, there are quite a few bugs filed for slow scrolling,
bug 100951 is supposedly being used to track these.
perhaps you might be able to associate this with one of those? ;)
Comment 2•24 years ago
|
||
Darin,
i'm not seeing a issue with w2k build for 12-18.. do you have a build # in mind
for linux?
| Reporter | ||
Comment 3•24 years ago
|
||
sorry, i should have mentioned the build id! i noticed this problem using the
2001121916 linux build, and it is very noticeable especially with the browser
window maximized.
| Reporter | ||
Comment 4•24 years ago
|
||
i just tried the 2001122008 build on a different linux box (733Mhz 256MB RAM)
and i could not reproduce the problem. scrolling on this machine only consumes
about 50% of the CPU. i'll try a newer build on the other linux box, and see if
that helps.
| Reporter | ||
Comment 5•24 years ago
|
||
yup! turns out the 2001122008 build does not exhibit this problem. i wonder
what fixed this...
marking WORKSFORME
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Comment 6•24 years ago
|
||
darin:
Could you test this via a remote X11 connection, please ?
You need to log in
before you can comment on or make changes to this bug.
Description
•