Closed Bug 7550 Opened 25 years ago Closed 25 years ago

Mousing over Javascript pre-cached images is ludicrously slow

Categories

(Core :: DOM: Core & HTML, defect, P3)

x86
Linux
defect

Tracking

()

VERIFIED DUPLICATE of bug 20110

People

(Reporter: zuperdee, Assigned: vidur)

References

()

Details

(Whiteboard: [Perf])

Using Red Hat 6.0, glibc 2.1, GTK 1.2.3, Linux kernel 2.2.9, and a CVS build of Mozilla from June 3rd. To reproduce: go to http://www.webtrends.com/. If you mouse over the images on the left side panel (which are laid out incorrectly too, BTW), the images seem to flicker and re-load about 3 or 4 times per mouseover, making it painfully slow. Sometimes after they are done flickering they disappear completely. And occasionally, it even crashes if I continue long enough.
Assignee: norris → vidur
Component: JavaScript → DOM Level 0
QA Contact: cbegle → gerardok
Status: NEW → ASSIGNED
Well, I don't see flickering, but there are a host of problems: 1) Layout is incorrect. There's spacing between the images that's significantly different from 4.x and makes the page look awful. 2) Pre-cached images (images created via the Image() constructor) don't seem to work. The bar on the side seems to load only when first displayed (you can see the image loading icon momentarily). 3) I don't see any flickering, but the performance of moving down the list is abysmal. This might either be event performance (care to take a look, Tom) or just that we're doing layout when we shouldn't or image display might be ludicrously slow. Either way, there's a problem here.
Hi, In case this sheds any more light on it, I just tried viewing the page with Netscape Navigator 3.04 too, and noticed that SeaMonkey is closer to the behavior that Navigator 3.04 exhibits on this page with respect to the layout than it is 4.x. You might just want to examine the differences in behavior between 3.x, 4.x, and SeaMonkey for some historical perspective on this problem.
Another good testcase for this bug can be found at http://www.mtn.co.za.
QA Contact: gerardok → elig
elig, yours?
QA Contact: elig → gerardok
Sorry, yours, or Prashant's. If the images load correctly on their own --- which they do --- ImageLib is working fine. Looks like a JavaScript problem to me.
Whiteboard: [Perf]
Blocks: 8691
with the latest NECKO build 199080408 on Linux RH 6, www.webtrends.com fails to load correctly. it seems to continuously reload itself over and over again.
Summary: Images flicker and reload 3 or 4 times per mouseover → Mousing over Javascript pre-cached images is ludicrously slow
Changing the bug summary so it more accurately states the problem. Also, should we spin off a new separate bug for the layout problem? (It still exists.)
Is this behaviour related to our GTK paint problems, or to the fact that we have no working cache? Vidur: when you say you saw no flicker, were you using Linux or Win32?
Status update: Since the time I originally filed the bug report, it seems the images no longer flicker on Linux. However, it still seems rather slow. And the layout issue still exists; there is a definite difference between SeaMonkey/Nova behavior that makes this page look awful in SeaMonkey.
Can you file another bug for the layout discrepancies? They shouldn't be attached to this one. Gagan: is there a bug to track cache issues? I couldn't find one, but we might want to be a dependent of such a bug.
Use 14050 for cache dependency. Although I am curious why mouse over images would rely on network cache. Shouldn't they be getting used from imagelib's cache? (even though network cache would hold the original compressed copies)
Okay, I've spun off a new bug for the layout issue - bug 14118.
Updating the URL to reflect the page I am referring to at its apparently new location.
In an attempt to get my bug list in order again, marking all the bugs I have currently as ASSIGNED.
DUPing with 20110. There definitely seems to be a need for profiling on rollovers. I'm fairly certain that images are getting precached in the image cache correctly (though I believe we need to profile image loading in general). The performance issues have more to do with event handling, style recomputation and relayout. *** This bug has been marked as a duplicate of 20110 ***
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
Marking verified as a dup after checking both. These are clearly the same and dealing with the performance javascript rollovers. #8691 depends on this bug, but not on the new one: #20110 Not sure if that is a problem
You need to log in before you can comment on or make changes to this bug.