22374 - m12 segfault in gtk

Status: VERIFIED WORKSFORME

(SeaMonkey :: General, defect, P1)

Description

[andre]

I just got the Milestone 12 and although It looks far better... it keeps
seg-faulting on me
<copy & paste>
Document http://www.compunity.com/itempg.php?ITEMID=125263&SID=39a7d719fe3bcb35b
744046a435a021c loaded successfully
Document: Done (7.085 secs)
WEBSHELL+ = 5
WEBSHELL+ = 6
WEBSHELL+ = 7
Loading pref-appearance.xul...
Looking up prefwindow object...
Creating prefwindow object......created
Gtk-CRITICAL **: file gtkwidget.c: line 1516 (gtk_widget_hide): assertion `widge
t != NULL' failed.
Gtk-CRITICAL **: file gtkwidget.c: line 1434 (gtk_widget_show): assertion `widge
t != NULL' failed.
Gtk-WARNING **: invalid cast from (NULL) pointer to `GtkMozBox'
.//run-mozilla.sh: line 29: 26760 Segmentation fault      $prog ${1+"$@"}

Comment 1

[Eli Goldberg]

Mcafee, from a quick scan, it looks like there's some kind of widget crash
happening semi-reproducibly; e.g. this bug, 22412, 19319, 18823, 22170.

However, most of these are sitting in browser-general without an engineer, so
they probably didn't get looked at.

Comment 2

[don]

Chris, find out whether this is a crash in widgets or CC&P.

Comment 3

[Stuart Parmenter]

I'd need to see a stack trace running with --sync  (you'll need to run mozilla-
bin with --sync since the mozilla script won't allow you to run with --sync (or
add it to the run-mozilla script)

Comment 4

[Stuart Parmenter]

making elig the QA contact since it didn't have one... he can assign it to
whomever.

Comment 5

[Chris McAfee]

This URL loads Ok for me on Linux, it is a little slow though.
I don't see the gtk warnings.

Comment 6

[Chris McAfee]

This works on WinNT also.
I'm marking this worksforme.  Please give me gtk version
info if this is still happening for you.  I have gtk 1.2.3.

Comment 7

[Eli Goldberg]

[e-mail], if you're still seeing this problem, could you please re-open

this bug with answers to pavlov & mcafee's questions?



Thanks!

Comment 8

[andre]

I tried out the nightly build from yesterday (05-01-1999) and I can use the
application again. This bug is gone, no segfault anymore! ;-)