308512 - Segfault on login attempt

Status: RESOLVED FIXED

(Firefox :: General, defect)

Description

[Max Powers]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050912 Firefox/1.6a1
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9a1) Gecko/20050912 Firefox/1.6a1

Firefox crashes upon successful entering of your password on my schools login
course site. Error output is as follows:

(Gecko:6040): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in
cast to `GtkWidget'

(Gecko:6040): GLib-GObject-WARNING **: invalid uninstantiatable type `(null)' in
cast to `GObject'

(Gecko:6040): GLib-GObject-CRITICAL **: g_object_get_data: assertion
`G_IS_OBJECT (object)' failed
/usr/share/firefox/run-mozilla.sh: line 131:  6040 Segmentation fault     
"$prog" ${1+"$@"}

Reproducible: Always

Steps to Reproduce:
1. Click on Login
2. Enter username and pass
3. Click submit

Actual Results:  
Browser crashes

Expected Results:  
To be logged into course website

Naturally it would be nice if I could give my pass for better testing, but alas
not that is not possible.

Comment 1

[Max Powers]

Also plagues latest branch (Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8b4)
Gecko/20050914 Firefox/1.4)

Here is the output from branch:

(Gecko:6106): GLib-GObject-WARNING **: invalid uninstantiatable type `gint' in
cast to `GtkWidget'

(Gecko:6106): GLib-GObject-WARNING **: invalid uninstantiatable type `gint' in
cast to `GObject'

(Gecko:6106): GLib-GObject-CRITICAL **: g_object_get_data: assertion
`G_IS_OBJECT (object)' failed
Warning: Cannot convert string "-adobe-helvetica-medium-r-*-12-*" to type FontStruct
Warning: Cannot convert string "-adobe-helvetica-bold-r-*-12-*" to type FontStruct
Window manager warning: Window 0x2a0004b (Welcome to) sets an MWM hint
indicating it isn't resizable, but sets min size 1 x 1 and max size 2147483647 x
2147483647; this doesn't make much sense.
/usr/share/firefox/run-mozilla.sh: line 131:  6106 Segmentation fault     
"$prog" ${1+"$@"}

Comment 2

[Reed Loden [:reed]]

Umm, why was this bug resolved as "FIXED". No indication was made as to how this was "FIXED" and why it shouldn't just be "INVALID" / "WORKSFORME"?

Comment 3

[Max Powers]

Umm, because this bug does not show up with the latest release of FF. I assume as thus it was fixed somewhere down the line between the time I reported it and one of the RC's that I tested that no longer showed the problem.

Change it whatever suits the bug better, doesnt matter to me. I just wanted to get it out of rotation. Though I have not tested this on the trunk builds, the branches no longer show this behaviour...