271831 - crash if I add a contact selected from the address book (using +adress button) from compose window

Status: RESOLVED EXPIRED

(Core :: Widget: Gtk, defect)

Description

[Igor Feghali]

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

When trying to add a contact address to a message, mozilla crashes.

opening adress book first and using "compose" button is ok, but when you try to
add a contact to the field "to" on the already opened compose window, mozilla quit.

Reproducible: Always
Steps to Reproduce:
follow the steps from mozilla-mail:
-click compose
-click +address
-select a contact
-click TO and OK

Actual Results:  
mozilla navigator and mail closes with no error messages

Expected Results:  
allowed me to write my email and sent the message.

Comment 1

[MarvinT]

I'm seeing the same thing:
> Reproducible: Always
> Steps to Reproduce:
> follow the steps from mozilla-mail:
> -click compose    [Or Ctrl-M to start compose window]
> -click +address
> -select a contact [Or selecting multiple contacts]
> -click TO and OK  [Or "Cc" or "Bcc" followed by "Ok"]

I ran it in GDB, and with a breakpoint at 'exit' see:
  #0  0x42029bb6 in exit () from /lib/tls/libc.so.6
  #1  0x40259545 in gdk_beep () from /usr/lib/libgdk-1.2.so.0
  #2  0x402fb21b in _XError () from /usr/X11R6/lib/libX11.so.6
  #3  0x402f81ca in _XEventsQueued () from /usr/X11R6/lib/libX11.so.6
  #4  0x402eb578 in XPending () from /usr/X11R6/lib/libX11.so.6
  #5  0x40266e17 in gdk_wm_protocols_filter () from /usr/lib/libgdk-1.2.so.0
  #6  0x4029ad7c in g_get_current_time () from /usr/lib/libglib-1.2.so.0
  #7  0x4029b124 in g_main_run () from /usr/lib/libglib-1.2.so.0
  #8  0x401a627f in gtk_main () from /usr/lib/libgtk-1.2.so.0
  #9  0x418abf36 in NSGetModule ()
     from /usr/local/mozilla/components/libwidget_gtk.so
  #10 0x41891784 in _Unwind_Find_FDE ()
     from /usr/local/mozilla/components/libnsappshell.so
  #11 0x08057364 in getCountry(nsAString const&, nsAString&) ()
  #12 0x08057ec0 in main ()
  #13 0x42015574 in __libc_start_main () from /lib/tls/libc.so.6

I managed to set a breakpoint at '_XError' and determined that 'gdk_beep' is
printing this:

   Gdk-ERROR **: BadPixmap (invalid Pixmap parameter)
     serial 30078 error_code 4 request_code 54 minor_code 0

immediately before it stops at the breakpoint at 'exit'.  At this point I can
avoid the problem like this:

   (gdb) up
   #1  0x40259545 in gdk_beep () from /usr/lib/libgdk-1.2.so.0
   (gdb) return
   Make selected stack frame return now? (y or n) y
   #0  0x402fb21b in _XError ()
      from /usr/X11R6/lib/libX11.so.6
   (gdb) continue

And then everthing works as expected!   In fact, I can then launch the address
book and doesn't call '_XError' but I *do* see the following messages (not seen
before the "continue") while hilighting multiple addresses, but that may be just
a timing issue:

   Gtk-CRITICAL **: file gtkdnd.c: line 2052 (gtk_drag_set_icon_default):
assertion `context != NULL' failed.
    
   Gtk-CRITICAL **: file gtkdnd.c: line 2052 (gtk_drag_set_icon_default):
assertion `context != NULL' failed.
 
BTW, this is from Redhat 9.0 on a AthlonXP
	Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8a4) Gecko/20040927

Hmmm.  Okay, the compose window was sitting there while I typed this (in "vi")
and after ~3 minutes it disappeared with a feedback agent (which I stupidly
dismissed, gaah!).  And it wasn't repeatable the second try.

Regards,
Marvin

Comment 2

[timeless]

please run again w/ gdb and w/ --sync, see the mozilla debugging faq and various
other bugs which talk about XError and --sync.

Comment 3

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 4

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.