7542 - popup crashes on multivisual display

Status: VERIFIED WONTFIX

(Core :: XUL, defect, P3)

Description

[tor]

Using a popup listbox, such as the pulldown on www.news.com, on
an X server capable of multiple visual types (8-bit and 24-bit
simultaneously) causes viewer/apprunner to crash with an
BadMatch X error.  The program manages to render the listbox
and grab the pointer before things start going downhill.
A stack trace is attached to this report.

Comment 1

[tor]

Attachment: stack trace

Comment 2

[stuartp]

*** Bug 7725 has been marked as a duplicate of this bug. ***

Comment 3

[leger]

Moving all Widget Set bugs, past and present, to new HTML Form Controls
component per request from karnaze.  Widget Set component will be retired
shortly.

Comment 4

[stuartp]

moving to XP Toolkit/Widgets since these are not HTML form controls

Comment 5

[tor]

Now that you're at netscape and have access to workstations supporting
multiple visuals, have you had a chance to reproduce the problem?

Comment 6

[Stuart Parmenter]

*** Bug 10229 has been marked as a duplicate of this bug. ***

Comment 7

[Stuart Parmenter]

I will try and look at this in more detail for M10.  I havn't been able to
reproduce this in my short simple tests though.  I will do more tests.  What
kind of display, etc is this?  I don't know much about sun systems...

Comment 8

[tor]

My testing happens to be on a Creator3D framebuffer, but in my experience
all 24-bit workstation framebuffers (HP, DEC, SGI, Sun, IBM) support
multiple bitdepths simultaneously.  Just look at the output of "xdpyinfo"
and see if it has different visual depths.  If so, you're probably in good
shape to reproduce the problem.

In case this gives you a clue as to what's happening: if you turn on the gfx
widgets, the same drop-down works fine and doesn't kill apprunner with a
badmatch.

Comment 9

[Stuart Parmenter]

mcafee, slamm: can you take a look at this as you are both more familier with
sparcs than I am (and you both have them)

Comment 10

[Chris McAfee]

wensleydale or worms might be good for testing this.

Comment 11

[Chris McAfee]

m11

Comment 12

[Chris McAfee]

Solaris in m12 for me.

Comment 13

[James Everingham]

Not necessary for dogfood.  Yell at me if you disagree.

Comment 14

[James Everingham]

Not necessary for dogfood.  Yell at me if you disagree.

Comment 15

[Chris McAfee]

m12

Comment 16

[don]

Move to M13

Comment 17

[leger]

claudius, does this happen with Linux 6.0?

Comment 18

[Stuart Parmenter]

it won't happen on linux 6.0 unless you have a multivisual display, which most
PC hardware and setups won't have.  You will need to test this on something like
a sparc.   Tor, is this still happening?

Comment 19

[tor]

This bug only happened with the native widgets, not the gfx ones.
It appears that the code for the native gtk widgets has decayed
to the point where they don't work at all (crashing dereferencing
null pointers, etc.).

Comment 20

[Chris McAfee]

Not interested in chasing native gtk bugs for beta,
do we not see this now that gfx has taken over?
maybe we should mark this as won't fix?

Comment 21

[don]

Move to M15 ...

Comment 22

[Claudius Gayle]

I vote for WONTFIX but I'd like to know what the 'official' decision is on these sort of bugs.

Comment 23

[leger]

Adding "crash" keyword to all known open crasher bugs.

Comment 24

[Chris McAfee]

marking won't fix per tor's comment.

Comment 25

[Claudius Gayle]

c'est la vie. marking VERIFIED.