Closed Bug 287565 Opened 19 years ago Closed 19 years ago

crash when filing a message while a message is being sent to the smtp server [@ nsMenuFrame::Notify]

Categories

(Thunderbird :: Message Compose Window, defect)

Product:
Thunderbird
Component:
Message Compose Window
Platform:
x86
Windows 2000
Type:
defect
Priority:
Not set
Severity:
critical

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 241733

People

(Reporter: jhebert, Assigned: mscott)

Details

(Keywords: crash)

Crash Data

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.5) Gecko/20041107 Firefox/1.0

The root cause may or may not be related to 215275, but the symptom is QUITE
different.  Therefore, I am opening a new bug.

When configured to use a secure SMTP server (SSL), the amount of time to
establish a connection is longer (many seconds).  The email being sent is plain
text or html, with or without attachments.  If you try to file the email to a
folder while the outgoing email is being sent to the smtp server, thunderbird
SOMETIMES crashes.  This is repeatable, but is not repeatable "at will".

I have a number of folders, with a few levels deep.  I right click the email,
select "Move to", pick one of the 3 email accounts I have configured, then work
my way down to the desired folder.

While moving through these menu selections, the outgoing email connects to the
smtp server and proceeds to send the message.  The message actually goes out
(successfully sent to the smtp server and delivered), the outgoing message gets
filed in the Sent folder, then thunderbird crashes.

Most of the time, there is no error message displayed, not even a default
Windows messages about a failed client.

Reproducible: Sometimes

Steps to Reproduce:
1.  Configure the SMTP server to use SSL
2.  I have 2 email accounts setup, plus the "Local Folders" account.  Not sure
if this is relevant, but it is what I am using.
3.  Have some messages in the Inbox. (not sure if this is relevant, but I
usually have less than 10, certainly less than 20)
4.  Select one of the mssages, perhaps the latest one or one that is "near" the
latest.
5.  Click the "reply" button at the top of the window (not sure this is
relevant, but is what I do)
6.  Type some text in the message and click send.
7.  While thunderbird tries to connect to the SMTP server (in my case this can
be 5 seconds or more), right click (on the message to which you are replying) in
the main window.  Start working your way through the "Move To" menu so you get
closer to your intended folder.
8.  Before you get to the desired folder, the SMTP server connects and the
outgoing email is sent.
9.  You are then unable to continue moving through the "Move To" menu item in
attempting to file the message.  Thunderbird crashes or exits after the email is
successfully sent to the server and filed in the Sent folder.

When this bug does NOT surface, the "Move To" menu will disappear and you can
repeat the steps to file the message as desired.

When this bug DOES surface, thunderbird crashes or exits.

Actual Results:  
When this bug does NOT surface, the "Move To" menu will disappear and you can
repeat the steps to file the message as desired.

When this bug DOES surface, thunderbird crashes or exits.

There are no error messages to report.  Thunderbird is no longer running and
needs to be restarted.

Expected Results:  
Send the message and allow the email to be filed.
If there is a major timing problem to make this impractical to fix, then the
main window should not allow the "Move To" operation while an outgoing message
is in progress.

There are no error messages to report.  The app crashes or exits.
jhebert@ulticom.com: Could you provide Talkback incident ID?
Keywords: crash
Question was:  "Could you provide Talkback incident ID?"

Sorry, but no.  I did not go through the Talkback approach.  I went through the
[long] list of bug reports and did not see any that were the same problem.  The
closest one I noticed was 215275 as indicated in the description.  I then opened
this bug report.

Please send me an email if I did not follow the correct process.  I apologize if
this procedure was not correct.

Thank you.
jhebert@ulticom.com: talkback id is acquired by running
/Thunderbird-program-directory/components/talkback.exe
Can you say what build you're running? 1.0? And if so, can you try a recent
trunk build? I fixed a bug in the copy code that could be related about a week ago.
Yes, it is version 1.0.  Sorry I did not supply that when opening the bug.
The "about" window shows "version 1.0 (20041206)".

I'll give the new trunk version a try.  I assume I can upgrade to the trunk
version, and if there are difficulties, revert back to 1.0 without losing any
data or settings.  Please let me know if this is NOT correct.

Thanks
Version: unspecified → 1.0
yes, you can go back and forth - the one possibility of problems has to do with
rss feeds. I'm not sure if the 1.0 feed list is compatible with the trunk feed
list. You wouldn't lose actual messages, but the feeds might stop working.
Though that could be fixed by now; I just don't know.
I tried "version 1.0.2 (20050317)" moments ago (info from Help->About window). 
I only tried this one time before having to restart the application.

I followed the how to repeat by replying to a message in the inbox, then trying
to file the message while waiting for the outgoing message to connect to the
smtp server.

Once it connected and sent the email, the "Move to" menus disappeared.  This is
consistent with the conditions of this bug report when the crash does not occur.
 However, I tried to repeat it, but could not send a message.

That is, after the how to repeat steps and the move-to menu going away, I tried
to "Reply" again.  Unfortunately, nothing happened.  I then tried to select
another message and still could not reply.  I noticed the message display
portion of the window (my options are set to have a left side for folders,
top/right for message summaries, and bottom/right for the selected message
contents) is "messed up".  The email headers are not visible, and selecting a
new message does not change the message display.

It also is somewhat stuck as I cannot retrieve emails (click "Get Mail", nothing
happens).  Select other folders (such as Sent), and the top/right message
summary portion changes correctly, but the message display still does not change
(bottom/right portion of the window).

So I exited the window (the only window that is visable) and tried to restart
Thunderbird.  However, it would not restart "properly" as I was prompted for
another profile.  I only have one profile defined so this was a surprise.  I
selected the default profile and it still would not start:  it said the profile
is already in use.

A look at the task manager (I am using Win2K) shows that thunderbird.exe is
still running, though not taking any time.  It may be stuck on a lock
(deadlock?).  Terminating this process and restarting thunderbird got me back to
normal.

I repeated the steps again and got the exact same behavior.

The symptom sounds like a deadlock, but I have no data to support that.  I
believe I have talkback enabled, but do not seem to have any data for you. 
There are no incidents to report, though I did have to kill the process.

Hope this helps!
I said a trunk build, not 1.02. 1.02 doesn't contain any of the fixes I mentioned.
Yes, you did say trunk build, my mistake :(.  I am not sure where to get that. 
Would it be:

http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/thunderbird-win32.zip
  

for a Win2K system?  I'll download and await your response before installing.

Thanks
yes, exactly, that's the one. I'm not promising it's fixed, but it might be fixed.
I installed "version 1.0+ (20050404)", which is from
http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-trunk/ThunderbirdSetup.exe


I also tried "thunderbird.exe" from thunderbird-win32.zip in the same location.
 Same results, which are as follows:

I cannot even "Reply" as the window pops-up, but nothing is in the To: fields,
and I cannot type in them either.

I deleted the *.msf files from the mail folder directory and retried.  Same
result -- cannot enter any addresses.

Same result for "Write", this issue is not restricted to "Reply".

I will reinstall 1.0.2.


ugh, the 04/04 build is bad, for other reasons. The 04/06 build should be better.
I just tried the following trunk build and got the same result -- unable to send
any email (as described above):

ThunderbirdSetup.exe                      07-Apr-2005 15:27   5.9M  

I just tried the build you requested -- 1.1a1.  Good news and bad news.

Good news:  I repeated the steps about 7-10 times and could not make it crash. 
Though this is not really enough attempts to prove anything conclusively, it
seems the bug that resulted in the crash may indeed be resolved.  I will test
some more to confirm.

Bad news #1:  After repeating these steps 7-10 times, thunderbird eventually got
very confused.:
    1.  It no longer obtained addresses from the address book or from the LDAP
server.  I could type in the "To:" line, but it did not resolve addresses.
    2.  I then tried to restart thunderbird by selecting "File-->Exit".  The
window went away, but the process remained.  I had to kill it through the task
manager in order to be able to restart thunderbird.

Bad news #2:  Upon installation of this version, my pop server settings were not
properly maintained.  I had a secure server for sending messages, and a normal
server for receiving.  After installation, the pop/smtp server addresses were
correct, but the pop server was changed to "SSL" being selected.  If I changed
it such that either SSL was not used, or I specified the secure server,
thunderbird was then able to send/receive as expected.
I don't know why the pop3 ssl setting got confused - I haven't heard any reports
of that. I don't suppose you can reproduce that.

Re the addressing widget problem, once you're in this state, if you look at the
javascript console, do you see anything? My only wild guess at this point is
that you've somehow used up your ldap connections - if you start a dos prompt
and type netstat, does it show a lot of open connections to your ldap server?
The other possibility is that the compose window address widget is messed up. If
you're in this state where the first compose window is messed up, can you leave
the first window open *and* open a second compose window and use it? 
I did not try to reproduce the pop3 SSL issue as it was not worth my time :).  I
mentioned it solely for your benefit prior to making this version generally
availble.

I am pretty sure there were few or no connections to the ldap server.  I
restarted the system, then installed thunderbird, then ran the test, which
consisted of 7-10 emails.  Each contained only one address, meaning there should
have only been 7-10 connections max (and then only if thunderbird did not
release them).

Also, though I cannot be sure, you may be drawing incorrect conclusions
regarding the compose widget being messed up.  I failed to mention that I did
indeed try to close the window (by clicking the corner X) and retry with a new
window.  Same result.  It was at that time that I decided to restart
thunderbird.  I did not actually try to leave the "bad" window running and try
another one in parallel.

Please remember that I was UNABLE to exit thunderbird as it was hung on
something.  It don't believe it was taking CPU time, but am not certain.  The
window did indeed go away, but thunderbird.exe was still running in the win2k
task manager.

I don't think this was a problem of 'N' occurrences or iterations, but rather
one of timing.  I have no data to support this, but it seems as though the root
cause of my original symptom (the crash) may have left things in an
unknown/unhealthy state; so now the application hangs (since it no longer
crashes).  Take this statement with a grain of salt though, not as a fact :).
I should have explained that if you open a compose window and close it, we don't
actually destroy the window, we just clear it out, and re-use it when you
compose a new message. That's why I said to actually have two windows open.
Please note that I just got thunderbird to crash as per the original complaint.
 This time, I reported a talkback incident as well.  Unfortunately, I do not see
a talkback ID and do not know where to get it.

Thus, please note that this problem remains in build 1.1a1.

Thank you.
if you to the thunderbird install directory and run talkback (c:\program
files\mozilla thunderbird\components\talkback.exe), it can show you the incident
id's you've reported.
Please see Talkback incident ID TB6829374Q for the latest crash (with build 1.1a1).
Incident ID: 6829374
Stack Signature	nsMenuFrame::Notify eaec21f6
Product ID	ThunderbirdTrunk
Build ID	2005053113
Trigger Time	2005-06-20 08:36:19.0
Platform	Win32
Operating System	Windows NT 5.0 build 2195
Module	thunderbird.exe + (00233c3a)
URL visited	
User Comments	Testing build 1.1a1 for bugzilla #287565. I reported the crash had
not yet occurred, but after an additional 15-20 times, the app crashed. Please
note that this may be related to a timing condition between having the "move to"
sub-windows being popped
Since Last Crash	11777 sec
Total Uptime	11777 sec
Trigger Reason	Access violation
Source File, Line No.
e:/builds/tinderbox/thunderbird-trunk/WINNT_5.0_Depend/mozilla/layout/xul/base/src/nsMenuFrame.cpp,
line 1295
Stack Trace 	
nsMenuFrame::Notify 
[e:/builds/tinderbox/thunderbird-trunk/WINNT_5.0_Depend/mozilla/layout/xul/base/src/nsMenuFrame.cpp,
line 1295]
nsTimerImpl::Fire 
[e:/builds/tinderbox/thunderbird-trunk/WINNT_5.0_Depend/mozilla/xpcom/threads/nsTimerImpl.cpp,
line 407]
PL_HandleEvent 
[e:/builds/tinderbox/thunderbird-trunk/WINNT_5.0_Depend/mozilla/xpcom/threads/plevent.c,
line 699]
SETUPAPI.DLL + 0x30c24 (0x778b0c24)

Not sure this helps, but here is another talkback ID for this problem, TB9513584M
Summary: crash when filing a message while a message is being sent to the smtp server → crash when filing a message while a message is being sent to the smtp server [@ nsMenuFrame::Notify]

*** This bug has been marked as a duplicate of 241733 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Version: 1.0 → Trunk
Crash Signature: [@ nsMenuFrame::Notify]
You need to log in before you can comment on or make changes to this bug.