Closed Bug 287489 Opened 20 years ago Closed 19 years ago

Crash when clicking on address area, or after entering name

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Linux
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: bill.sheppard, Assigned: mscott)

Details

(Keywords: crash)

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041109 Firefox/1.0
Build Identifier: version 1.0.2 (20050317) for Linux as downloaded from mozilla.org

Running on SuSE 9.0, 2.4.26 kernel, Pentium M:

Occasionally (I haven't been able to find concrete steps to reproduce)
Thunderbird will crash while I'm composing an email.  It always happens either
when I first click in the address entry area, or after typing a name at the
point where Thunderbird fills in the full name (based on an Address Book entry).



Reproducible: Sometimes

Steps to Reproduce:
1. Click in address entry area

or

1. Enter name in address area, tab off of space

Actual Results:  
All Thunderbird windows close

Expected Results:  
No crash

I don't think this is of much help, but I ran it with debugging turned on,
here's the end of the output from gdb:

[New Thread 278546 (LWP 23046)]
[New Thread 294931 (LWP 23047)]
[New Thread 311316 (LWP 23214)]
[New Thread 327701 (LWP 23278)]
[New Thread 344086 (LWP 23667)]
[New Thread 360471 (LWP 23887)]
[New Thread 376856 (LWP 23888)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 21971)]
0x83e58955 in ?? ()

I'm happy to do this with more information if someone can tell me how to extract
extra useful data.
Please provide a talkback ID ,,
I don't have one - when starting up as non-root I get "(QFA)Talkback error:
Can't initialize.".  I've changed all ownership in /opt/thunderbird to my user,
but still get this error.  Any suggestions?
Keywords: crash, stackwanted
Found another mode to induce the crash.  I replied to a message, entered some
text, then clicked on the "To" dropdown in the second row (since the first one
was already filled in with the original message sender).  The system crashed
upon clicking on "To".

I'm now running Thunderbird as root so hopefully next crash I'll get a Talkback
ID.  Is there something else I should be doing from gdb when the system crashes,
or will having Talkback be sufficient?
More information:

Running Thunderbird as root.  Composing a new email, entered part of a
recipient, received a drop-down list of matching entries.  Arrowed down to my
choice, pressed "return", Thunderbird crashed.  Received a bit of additional
information from gdb:

[New Thread 950331 (LWP 28346)]

Program received signal SIGSEGV, Segmentation fault.
[Switching to Thread 16384 (LWP 15699)]
(gdb) backtrace
#0  0x4058ab3b in nsQueryInterface::operator()(nsID const&, void**) const ()
    from /opt/thunderbird/libxpcom.so
#1  0x4058ac33 in nsCOMPtr_base::assign_from_qi(nsQueryInterface, nsID const&)
    () from /opt/thunderbird/libxpcom.so
#2  0x083f3cbe in nsPRUint32Key::Clone() const ()
#3  0x083f3e7c in nsPRUint32Key::Clone() const ()
#4  0x083f3c23 in nsPRUint32Key::Clone() const ()
#5  0x083f31cf in nsPRUint32Key::Clone() const ()
#6  0x0844241b in nsPRUint32Key::Clone() const ()
#7  0x080a21d4 in ?? ()
#8  0x090a30c8 in ?? ()
#9  0x0dca9fc0 in ?? ()
#10 0x0d33f150 in ?? ()
#11 0x0b23eb48 in ?? ()
#12 0xbfff9328 in ?? ()
#13 0x00000006 in ?? ()
#14 0xbfff935c in ?? ()
#15 0x405e2dc4 in __pthread_lock () from /lib/i686/libpthread.so.0
#16 0x08093442 in ?? ()
#17 0xbfff97ec in ?? ()
#18 0x0dcaa27c in ?? ()
#19 0x0d363668 in ?? ()
#20 0x09098518 in ?? ()
#21 0xbfff9428 in ?? ()
#22 0xbfff9420 in ?? ()
#23 0xbfff9420 in ?? ()
#24 0xbfff9438 in ?? ()
#25 0x4058ab3d in nsQueryInterface::operator()(nsID const&, void**) const ()
   from /opt/thunderbird/libxpcom.so
#26 0x08092641 in ?? ()
#27 0xbfff97ec in ?? ()
#28 0xbfff948c in ?? ()
#29 0x0dcaa27c in ?? ()
#30 0xbfff965c in ?? ()
#31 0x0ba05da0 in ?? ()
#32 0xbfff962c in ?? ()
#33 0xbfff94e0 in ?? ()
#34 0xbfff9498 in ?? ()
#35 0x4058ac33 in nsCOMPtr_base::assign_from_qi(nsQueryInterface, nsID const&)
    () from /opt/thunderbird/libxpcom.so
#36 0x080a55b1 in ?? ()
#37 0xbfff97ec in ?? ()
#38 0xbfff9614 in ?? ()
#39 0xbfff973c in ?? ()
#40 0xbfff961e in ?? ()
#41 0xbfff965c in ?? ()
#42 0x0ba05da0 in ?? ()
#43 0xbfff962c in ?? ()
#44 0xbfff970c in ?? ()
#45 0xbfff965c in ?? ()
#46 0x08d2a1a8 in ?? ()
#47 0xbfff95b4 in ?? ()
#48 0x400304a2 in JS_GetStringChars () from /opt/thunderbird/libmozjs.so
#49 0x080ab6a1 in ?? ()
#50 0xbfff97ec in ?? ()
OK, I was able to get a Talkback.  Incident #TB4582409G.  This is the fifth time
today I've had this crash, I lost 30 minutes worth of email under composition
this time...
hmm, this stack is difficult for me, a developer should look at the stack

http://talkback-public.mozilla.org/talkback/fastfind.jsp?search=2&type=iid&id=TB4582409G
Keywords: stackwanted
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/
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.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.