139271 - Occasional display glitches - S3 video, Portege laptop

Status: RESOLVED DUPLICATE of bug 115452

(Core :: Graphics: ImageLib, defect)

Description

[David Gerard]

From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc1) Gecko/20020420
BuildID:    2002042006

I'm getting some display glitches I've never seen before on this
Win98 laptop that I don't get with the same build on the Win2k box
upstairs.

The glitches go away if you refresh the page, or if you minimise and
then maximise the Mozilla window in question.

Build: 2002042006, 1.0 branch.

I suspect weird libpr0n interaction with the display hardware.
(Could be completely wrong of course.)


Reproducible: Sometimes
Steps to Reproduce:
1. Open a page.


Actual Results:  Sometimes there's weird rubbish on parts of the display, like a
piece of memory has been put directly on the screen.

Expected Results:  No such weird rubbish on parts of the display.

Laptop: Toshiba Portege 3440CT, Win98SE, 64MB memory.

Video hardware: S3 Inc. Savage/IX w/MV
Manufacturer: S3
DAC type: Internal
Memory: 8 MB
Features: DirectDraw 1.00
Software version: 4.0
Current files: s3_7.drv,*vdd,*vflatd,s3vdd7.vxd,s3_7.dll

Hardware acceleration: Full

I'll attach a pile of screen shots of examples.

Comment 1

[David Gerard]

Attachment: Example of display glitch

Comment 2

[David Gerard]

Attachment: Attachment 80248 image, without glitch

Comment 3

[David Gerard]

Attachment: Another example glitch

This one is at the top of the window, while the page is loading. The Bug List
loading in the other tab is *huge* and sent Win98 into terminal thrashing
for about ten minutes :-)

Comment 4

[David Gerard]

Attachment: Another example

This one is on a large loading page. The glitch cleared when the page loaded.

Comment 5

[David Gerard]

Attachment: Example of glitch in the chrome

This one is a glitch in the chrome - the top of the menu bar.

Comment 6

[David Tenser [:djst]]

Could this be related to the drivers for your video card? Video card glitches
can appear this way, I think.

Comment 7

[David Gerard]

Well, I do suspect a driver interaction :-)

But I reported it because it happens really quite a lot with Mozilla (from
original reported build through to 1.0-final, which I'm using right now) and
not with any other app in the system.

So if it is a driver interaction, it's some interaction between either gecko
and the driver, or libpr0n and the driver. Presumably. Guessing. Hence adding
the driver (and laptop) type to the summary.

Doing a search on 'S3', I find one other bug: bug 115452 - though the glitches
I'm seeing are much worse (see my attachments) - not sure if this counts as a
dupe of that bug or of its dupes (bug 101907, bug 138445). As bug 101907 says,
"there's definitely an issue with Mozilla/GTK/Win32 and S3 Savage* graphic
cards." CC'ing Warner Young from S3 on this bug too, in case you have ideas or
test cases you'd like me to try.

Comment 8

[Kai Lahmann (is there, where MNG is)]

Reporter: Can you reproduce this bug with a recent build of Mozilla (for
example, 1.4 RC1)? If so, then please comment again with details. If not, then
please resolve this bug as WORKSFORME. Thanks.

Comment 9

[David Gerard]

Probably not in the next day or two (it's not my laptop and I'm not in that
house very often) but I'll see what I can arrange ASAP.

Comment 10

[Daniel Wang]

David, any news?

Comment 11

[Asa Dotzler [:asa]]

David, can you follow up here?

Comment 12

[David Gerard]

I'm afraid I have nothing to add here. I will ask the owner if they will install
a recent Firefox or something.

I suppose this could be closed, though if it shows up again for someone else
they then won't be able to check it ...

Comment 13

[David Gerard]

I have just emailed the laptop's owner most humbly requesting assistance.
I will report back to the bug. If she can't help, I'll close it.

Comment 14

[Robin Monks]

This appears *very* similar to bug 115452 so I'm am going to make a dupe.

Reporter, if you feel this bug is very different from bug 115452 please reopen.

Thanks

*** This bug has been marked as a duplicate of 115452 ***