Closed
Bug 149674
Opened 24 years ago
Closed 23 years ago
Odd repaint errors in Mozilla windows
Categories
(Core Graveyard :: GFX, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: tenchi1174, Assigned: kmcclusk)
References
()
Details
Ever since RC3 I've been experiencing nasty repaint errors in Mozilla. Some are
minor and annoying as can be viewed in the Location and vertical scroll bars:
http://www.geocities.com/tenchi1174/etc/MozillaRedrawErrors.png
Others have actually totally messed up my Windows display. Just a few minutes
ago Mozilla was in the middle of loading a large table. After about 15 seconds
odd boxes started popping up and all the currently open windows were shuffled
around the screen. This has happened with no other browser running.
Thanks,
- e!
tenchi1174@yahoo.com
The URL to screenshot is invalid.
Please include at which URL's this bug occures / steps to reproduce, and always
the latest build ID you see the bug with.
screenshot appears now. Which graphics card are you using?
Also: Can you please test if the error also displays with a clean installation
(after full uninstall/deleting components and chrome) and testing with a new
profile? (Also include build ID if testing with a newer build)
Actually, it's not invalid. For *some* reason Yahoo/Geocities gives an invalid
file message every other time. If you go to the page and reload then it pops up
OK. Yeah, I noticed this when I originally uploaded it. I was trying to stay
away from GIF and JPEG too. :(
Well, perhaps try the updated link where I've converted it into .gif...
http://www.geocities.com/tenchi1174/etc/MozillaRedrawErrors.gif
In direct response to the questions asked:
- Include at which URLs this bug occurs:
All.
- Steps to reproduce:
1) Load Mozilla.
2) Browse to any page that has more than 1 screenful or a form with a textarea.
3) For the scrollbar problems, just grab a scroll bar and move it up/down
or side/side.
- Latest build ID:
2002053012.
(Sorry, I didn't see a form field on the bug report for including this and I
probably did not RTFM. My bad.)
Thanks,
- e
tenchi1174@yahoo.com
> screenshot appears now. Which graphics card are you using?
Identity: S3 Graphics Inc. Savage/IX Display Driver
Memory: 8 MB
BIOS: 4.02.50.64
Driver date: 5/11/2001
Version: 5.12.1.7065
Various file details:
- C:\winnt\system32\drivers\s3savmxm.sys = 5.12.01.7065-7.40.35
- C:\winnt\system32\s3savmx.dll = 5.12.01.7065-7.40.35
And I think I'm using DirectX 8.0a.
> Also: Can you please test if the error also displays with a clean
> installation (after full uninstall/deleting components and chrome)
> and testing with a new profile? (Also include build ID if testing with
> a newer build)
I'll try uninstalling (again) and deleting the profile. When the problem
occurred one of the things I did was uninstall it and make sure the Program
Files directory for Mozilla got deleted. I didn't think about deleting the
configs from Documents and Settings. I'll do that and report back. This may be
a Savage IX thing? Although, it did totally screw up the windows one time so it
seems to be affecting whatever core GDI Windows has. (I forget the exact term.)
- e
tenchi1174@yahoo.com
Comment 5•23 years ago
|
||
reporter: can you reproduce this bug with a recent build of mozilla (for
example, 1.2)? if so, please comment again with details. if not, please resolve
this bug as WORKSFORME. thanks.
In recent builds I haven't seen the problem come back. Either it was fixed in
the code or I had a new driver---which, I actually couldn't tell you for certain.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Comment 7•23 years ago
|
||
thanks for the response.
when we are uncertain as to the exact fix, the correct resolution is WORKSFORME,
so I'll change that by reopening...
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---
Comment 8•23 years ago
|
||
... and resolving again.
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago → 23 years ago
Resolution: --- → WORKSFORME
Updated•17 years ago
|
Product: Core → Core Graveyard
You need to log in
before you can comment on or make changes to this bug.
Description
•