236.75 KB, image/png
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031031 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031031 If I scroll downwards on a Web page, the page display gets corrupted. It happens regardless of how I scroll (by dragging the scroll bar, by using the mouse wheel, or by using the page up/down buttons). I cannot get this to happen if I scroll upwards. It happens on a lot of pages: http://www.nytimes.com, http://www.cnn.com, http://www.slashdot.org, and even this mozilla bugzilla page that I'm currently entering this bug on (http://bugzilla.mozilla.org/enter_bug.cgi?product=Browser). I will attach a screenshot of a corrupted view of the bugzilla mozilla page for your perusal. I cannot get this problem to occur on http://www.google.com (more specifically, on search results pages). I can get the problem to go away by forcing a redraw of the page (I've been doing this by simply maximizing and then minimizing another window on top of the corrupted window). Earlier, I could also get the problem to go away by simply focusing on another window (this stopped working at some stage). I can also make the problem go away by highlighting the affected area. Reproducible: Always Steps to Reproduce: 1. Go to one of the sites I mentioned. 2. Start scrolling downwards (honestly, I'm not doing anything else). If you scroll at lightning speed, it won't occur. At slow or moderate speeds, it always occurs. Actual Results: The page looked corrupted. Characters, instead of simply moving up the screen, left a trail behind all the way to the bottom of the screen, or portions of the same text start appearing in multiple areas. Coloured bars (which I assume are table cells, but I don't know) sometimes repeat the same way. Machine: Dell Precision 650, dual 2.4GHz Xeon cpus (w/ hyperthreading), 2GB RAM Video: nVidia Quadro4 900XGL, using the nvidia driver, xinerama, two LCD screens X: XFree86-4.2.1-21 Kernel: 2.4.20-19.8smp Distribution: RH 8 This only started happening with Mozilla 1.5. I have never had this happen with previous versions of Mozilla. I installed this version by using the default built RH 8 rpms provided on the Mozilla downloads page.
Created attachment 136848 [details] Screenshot of my desktop showing the corrupted Mozilla window Corrupted view of mozilla bugzilla bug entry page
To be a bit more precise, I can get this to happen on cnn's and slashdot's home pages, but not on the NYT's home page: it happens on any story off the home page, though. I should mention that, apart from that one page I mentioned and provided a screenshot of, I cannot find any page in the mozilla.org site that causes this problem. I am happy to provide screenshots from other sites, if requested.
Reporter, have you tried a recent build? Either a nightly or 1.6 (if it's out by the time you read this) will do, but just try with a more recent build. You might also want to see if you can upgrade your video drivers. I've had this happen a few times, but nothing reproducable like this.
*** This bug has been marked as a duplicate of 169883 ***
This bug isn´t a duplicate of Bug 169883 ibm.com - While scrolling down the text get scrambled In the other bug there are a lot of URL´s where you can reproduce this behaviour, I didn´t see any URL in this bugs description. The URLs mentioned are wfm. When did this page corruption start? Right after installation? Is it reproducable, at a URL, right at the start of Mozilla, or only at the end of a long browser session? Is you Mozilla installed correctly, do you use extensions, themes? Does it happen only on websites using some sort of plugin, maybe Java, or Flash?
Sorry, I'm a bit of a n00b to duping bugs, not sure what levels of similarity to look for :D I wasn't able to reproduce the bug on the URLs given in the description, although I was able to reproduce the testcase in the other bug. I'll be more careful from now on.
All comment 0 links WFM in current Linux trunk.
This is an automated message, with ID "auto-resolve01". This bug has had no comments for a long time. Statistically, we have found that bug reports that have not been confirmed by a second user after three months are highly unlikely to be the source of a fix to the code. While your input is very important to us, our resources are limited and so we are asking for your help in focussing our efforts. If you can still reproduce this problem in the latest version of the product (see below for how to obtain a copy) or, for feature requests, if it's not present in the latest version and you still believe we should implement it, please visit the URL of this bug (given at the top of this mail) and add a comment to that effect, giving more reproduction information if you have it. If it is not a problem any longer, you need take no action. If this bug is not changed in any way in the next two weeks, it will be automatically resolved. Thank you for your help in this matter. The latest beta releases can be obtained from: Firefox: http://www.mozilla.org/projects/firefox/ Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html Seamonkey: http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above comment). If anyone thinks this is incorrect, they should feel free to reopen it.