193158 - Compose window freezes on send

Status: RESOLVED EXPIRED

(MailNews Core :: Composition, defect)

Description

[Robert Accettura [:raccettura]]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3b) Gecko/20030212

When I send mail using composer, the spell checker launches as normal (yes I did
upgrade to the latest), and checks mail.  Then sends.  the window doesn't close
though.  Just sits there.  Right clicking on the window in the taskbar doesn't
do anything either.  Can't close it, just stays until I quit the mozilla.exe
process.

I have norton installed, it does come up scanning outgoing email, the mail is
sent.  It's in the sent folder as well.

Should note nothing else is wrong except the window won't go away, and I can't
make it go away.  

Reproducible: Always

Steps to Reproduce:
1.  Write an email to someone you admire and love, just make sure it isn't
someone who has a restraining order against you.
2.  Be sure to say "I love you", but don't gross out creepy or anything.
3.  Send email.

Actual Results:  
The email is sent, but the compose email window doesn't close

Expected Results:  
Should close the window when done.

Comment 1

[Andrew Hagen]

-- Is the computer you are running Mozilla on running an antivirus program? If
so, please detail what program and what version it is. Temporarily disable the
antivirus program. Then try to reproduce the problem you describe. Does the
problem still occur?

-- Go to Edit | Mail & Newsgroup Account Settings | Outgoing Server (SMTP) and
check "never" on whether to use a secure connection (SSL). Now try to reproduce
the problem. Does it still occur?

-- Go to Edit | Mail & Newsgroup Account Settings. In the appropriate account,
under Copies & Folders, unselect "place a copy in." Now try to reproduce the
problem. Does it still occur? If this works, is this an IMAP account? Are there
many messages in the sent folder?

-- Is the computer behind a firewall? If so, temporarily disable it, or put the
computer directly on the Internet. Can you still reproduce the problem? If not,
what product and version number is the firewall?

-- Delete all your SMTP server entries. Exit Mozilla. Restart Mozilla. Recreate
all your SMTP server entries. Can you still reproduce the problem?

-- Do you have spellchecker installed? If so, disable it or remove it. Does that
solve the problem?

-- Is your profile hosted on a network drive (or NFS mount)? 

If none of these steps work, please attach an SMTP log. The steps for creating
the log can be found here:

http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#imap

Comment 2

[Robert Accettura [:raccettura]]

Seems to be spazzing as far as when it happens.  I haven't found any logic to it
yet.

I do have AV Software (norton 02), and it has happened while it was disabled.

POP account

No firewall

Tried removing spell checker, made no difference.

Will monitor this and see if I can get it to occour once again with SMTP logging.

Comment 3

[Kostub]

This happens to my compose window too. Occurs only with 1.4a, did not occur in
previous versions. 
OS: Windows XP
Mail is read through IMAP.

Comment 4

[Robert Accettura [:raccettura]]

Still happens on a rare occasion.  Perhaps once every 25 or so emails I send.  I
*still* can't find a pattern to it.  All I can say is "it happens".

Comment 5

[Mike Cowperthwaite]

Robert Accetura, have you followed any of the suggestions in comment 1?  Is this 
bug still a problem for you?  Have you upgraded to Mozilla 1.4 (or even 1.3 
final) yet?

Comment 6

[Robert Accettura [:raccettura]]

I still get this on a rare occasion.  I can't for the life of me figure out
what.  Tried disabling/enabling everything.  Even happened in a new profile.

I'm guessing this is just something to live with until Thunderbird hopefully
solves it.

Comment 7

[Kenan]

WFM on WinXP & Mozilla Build 2004061507 (POP3).

reporter: Can you reproduce the bug with the latest release?

Comment 8

[Kostub]

this is still a problem with Thunderbird version 0.6 (20040502) (IMAP).

this now happens everytime a mail is sent.

Comment 9

[Kostub]

this is still a problem with Thunderbird version 0.7 (20040616) (IMAP).

this now happens everytime a mail is sent.

Comment 10

[Kostub]

I found a workaround for this bug.

Set the following preference:

user_pref("mail.compose.max_recycled_windows", 0);

see  http://www.mozilla.org/mailnews/arch/compose/cached.html for details.
setting the compose window to not cache gets rid of this frozen window.

Comment 11

[Bharat]

Reporter, do you still see this problem with the latest Mozilla nightly (or even
Moz 1.7.3)? If not, and you only see this problem with Thunderbird, the
"Product" assignment for this bug needs to be changed appropriately.

Comment 12

[Kostub]

Confirmed this with Thunderbird 1.0.

Comment 13

[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 14

[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.