Bugzilla – Bug 113596
Gecko Rendering display slowdown
Last modified: 2005-09-04 08:54:09 UTC
I can't find THIS anywhere yet. FIrefox/Thunderbird/NVU...all gecko-based rendering applications cause a slowdown on the display on the laptop. Didn't happen in Beta 2. Can't find any indication that something is wrong, but it's confirmed that all other applications and operation is normal. CPU cycles seem to be about normal and not pegged..so it's in the display. There is a lag and hesitation when changing things within the application. I tried this with the provided rpm's and the standard zipped versions from mozilla...behavior is the same with both.
This is only on the ACTIVE desktop WITHIN the program. I noticed that if I go to another virtual desktop with other applications...all is normal, so the X-system isn't getting overloaded. This is very curious. When "changing" things such as opening and closing the sidebar, you get a black field for a split second and then it fills in...also with Thunderbird, while typing a message, there is a hesitation in the typing at times....Like it's bogged down. I'm thinking that this is more of a mozilla problem than an X problem or anything like that...but I cannont figure out what has changed from beta 2 to beta 3 to cause this, except for some newer libraries that it might not be playing nice with. I also suspect that this issue will not even be noticed on a fast machine, since the SPEED of the application isn't really slowed down as much as the CHANGE OF THINGS on the screen is. Don't know if this is making ANY SENSE AT ALL to you, but hopefully someone can confirm this. I will "update" my machine on Sept. 1st with new packages from beta 4...see if there is a differenct...after that, I'll format and do a clean install of beta 4 to see if it's back to normal. This was a clean install of beta 3. Just more information
Plan for clean install of beta 4 in a couple of days to see if there is a difference. Me thinks that mozilla isn't playing nice with some libraries...
yes, we should wait for beta4. I don't see this behaviour on beta3 though
Thank-you...I think that is the best solution for now...as it looks as if this is an isolated situation. I'm thinking that you guys can sort of just keep this bug laying around but tag it as potentially bogus, kind of...yeah...from the reporter, until he (me) does the work of investigating this a little further. Don't waste any time on this for now. IF I SEE the behavior later on a fresh install, I'll update this bug, but for now, we'll just leave it alone. Thanks, Wolfgang...
Wolfgang! Clean install of beta 4 and problem is GONE GONE GONE...this is now lightning fast. I don't know if I can close this bug officially, so can you do it? This bug is no longer...it is FIXED! Working perfectly now.
fixed according to comment