172668 - Crash on a number of pages within VNC session depending on port number

Status: RESOLVED INVALID

(Core Graveyard :: Embedding: GTK Widget, defect)

Description

[Antonio Piccolboni]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020826

Mozilla running within VNC crashes with this error
Gdk-ERROR **: BadMatch (invalid parameter attributes)
  serial 57 error_code 8 request_code 129 minor_code 3
when accessing certain pages in a highly reproducible fashion but depending on
port number on which the VNC server is listening. Believe it or not: port 99
crashes my yahoo home page, 98 a certain yahoo photo page and so on and so
forth. Seems to be independent from color depth as somebody suggested (did
throught testing). It looks like all pages had some graphical elements.

Reproducible: Sometimes

Steps to Reproduce:
1. Start VNC server, res 1600x1200, different ports, no other options specified
(default everything) vnc-3.3.3r2-28
2. Start vncviewer on a different machine (using TightVNC 1.2.3
3. Browse graphics heavy pages

Actual Results:  
Crash with message 
Gdk-ERROR **: BadMatch (invalid parameter attributes)
  serial 57 error_code 8 request_code 129 minor_code 3

Expected Results:  
Continue normally

Crash URL is a function of vncserver port selected, very reproducible, very weird.  
Independent of vncserver color depth option

Comment 1

[greer]

Reporter, can you reproduce with a talkback enabled build and supply a Talkback ID?

Comment 2

[Ned Boddie]

Confirmed as not working for me in the 1.2 release, I get the error:

java.lang.NullPointerException: name

It does work fine in the 1.2b Oct 16 release, I'm going to downgrade to that one
again :(

Comment 3

[gene smith]

Gdk-ERROR **: BadMatch (invalid parameter attributes)
  serial 51 error_code 8 request_code 129 minor_code 3

I also see this error on a vncviewer running on win98 and xserver on linux. All other apps
are fine in the viewer (e.g., konq). Upgrade from moz 1.0.1 to 1.3 had no effect. Matching 
win98 and linux screen res and color depth did not fix. Not all sites crash mozilla. Going 
to cnet.com seems to crash it (plus others I am sure).

Comment 4

[gene smith]

I just put in the previous comment and it is partially wrong. I did not actually
match the resolution of the vncserver to the win98 resolution. When I did the
problem went away. So I guess the only question is possibly why mozilla can't
tolerate a mismatch (BadMatch) and other apps (at least several I looked at) can.

Comment 5

[Alexander Opitz]

Reporter can you reproduce this bug with a newer build (1.4 final)?
If not, then please close this bug as worksforme. Thanks.

Comment 6

[Max Kanat-Alexander]

No reply in two months. Closing bug.

Reporter -- if you want to reopen the bug: Does this still happen with the new
VNC 4.0 beta? (RealVNC.com)

-M