Closed Bug 678323 Opened 14 years ago Closed 13 years ago

scrolling on pages with many pics or big <td>-elements is very slow or sluggish

Categories

(SeaMonkey :: General, defect)

SeaMonkey 2.2 Branch
x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: lahmbi56789, Unassigned)

Details

User Agent: Mozilla/5.0 (Windows NT 5.1; rv:5.0) Gecko/20110706 Firefox/5.0 SeaMonkey/2.2 Build ID: 20110706120824 Steps to reproduce: visit e.g. http://www.spieleprogrammierer.de/index.php?page=Thread&threadID=16246 the content on this page is not too complicated, mainly text Actual results: scrolling via scrollbar is really slow, it seems to take ages, until the page moves, especially when you try to scroll over a <td>-element containing a lot of text. scrolling by mouse wheel somewhat works, but feels very sluggish, as if something would be braking. Expected results: smooth scrolling, tested with Opera, where scrolling is quite smooth
Works fine with: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.1.20pre) Gecko/20110606 SeaMonkey/2.0.15pre and with: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:8.0a1) Gecko/20110812 SeaMonkey/2.5a1 Try testing in safe mode: Help->Restart with Add-ons Disabled.
Just tried, it's slightly better, but not really smooth. This issue is probably related to the new Firefox stuff in SeaMonkey 2.2.
Edit->Preferences Appearance->Content. Disable Hardware Acceleration and/or Enable smooth scrolling. Try playing around with these settings.
tried all combinations, hardware acc on/off, smooth scrolling enabled/disabled, it seems to make no difference. if this issue is fixed in upcoming releases like Seamonkey 2.3, it would be ok for me. I filed this bug mainly to give the devs hints for improvements and/or possible tests. I filed another bug for flickering layers in amazon pages ("look inside"). The point is that 2.0.14 was working really smooth, and I'd probably prefer the 2.0 series (2.0.15 coming soon?), as long as it's supported.
still the same with SM 2.4.1
Still the same with SM 2.5. It's a bit smoother in Firefox 8.0.1 and really smooth in Opera 11.52. Just try it in Opera, it's as different as day and night, compared to Seamonkey. In SeaMonkey it feels, as if something would be braking.
still the same with 2.7.1. Or it just me with my integrated graphics chip (notebok with admittetly weak ATI x1250)?
Probably. Go to about:support Scroll down to the bottom where the Graphics Section is. Cut and paste that section in a comment here. Also can you check if your graphics driver(s) is up to date?
Unfortunately it is in German, I'm trying to translate: ATI Radeon Xpress 1250 Vendor-ID 1002 Device-ID 7942 Card-RAM Unknown Card-Driver ati2dvag Driver-Version 8.423.0.0 Driver-Date 10-11-2007 Card-RAM (GPU #2)Unknown Card-Driver (GPU #2)UnknownWebGL-Renderer Blocked due to your driver version. Try to update to at least version 10.6 GPU-accelerated Window 0/1. Blocked due to your driver version. Try to update to at least version 10.6 Note that I'm not using two graphic cards or displays, this is just some weird config by the catalyst driver, it always shows 2 cards, which are in fact one and the same. Since the device is legacy for some years now, there won't be any updates. Still it is DX9.0c compliant. I've configured it in the BIOS to get 128 MB RAM. This issue wasn't there with Seamonkey 2.0.x, so I think it is a legitimate issue.
SeaMonkey 2.0 didn't use hardware acceleration. According to Google v10.6 drivers are available for ATI Radeon Xpress 1250.
Hi Philip, first of all, I have to admit, that I gave up on getting newer drivers years ago, as ATI clearly stated, that the chipset was legacy. I probably was a bit ignorant in that regard, but who could know, that ati would bring another driver after more than 2 years without update. But the latest driver I seem to be able to find on the ati page is 10.2, see http://support.amd.com/de/gpudownload/windows/Legacy/Pages/integrated_mce-xp.aspx?type=2.7&product=2.7.2.3.2&lang=English I will try that driver and come back in a few days. In general my opinion still is, that an app like SeaMonkey should run smooth even on older hardware and older drivers, but if I should be the only one with such an issue, I'll probably agree to close the bug.
Hi Philip, everything seems to be working fine with that driver for me, though it was a major pain to get it installed. Samsung won't update their drivers, so you have to manually choose that driver from a list that contains several "XPress 1200" entries as closest match, I chose the one with the closest matching Device ID (which of course isn't shown in the dialog), then you have to click away two or three warning about missing signatures, reboot, and everything's fine. I'm still thinking, that SeaMonkey should run well with older drivers, in the end it's just a browser, not a graphically bloated fp shooter, on the other hand I don't want to create more noise than necessary. So I'd say close the bug.
Thanks for getting back to us! Resolving as WORKSFORME.
Status: UNCONFIRMED → RESOLVED
Closed: 13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.