Closed Bug 72489 Opened 23 years ago Closed 16 years ago

sending email blocks the ui (and never gets sent)

Categories

(MailNews Core :: Backend, defect)

Product:
MailNews Core
Component:
Backend
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED WORKSFORME

People

(Reporter: sspitzer, Unassigned)

References

Details

Attachments

(1 file)

An strace of the command "mozilla -compose" outlining the freeze
116.44 KB, application/x-gzip
Details 
when I compose and send an email, it blocks the ui.

I'm getting this assertion:

###!!! ASSERTION: unable to create an output stream: 'NS_SUCCEEDED(rv)', file
nsMsgProtocol.cpp, line 176
###!!! Break: at file nsMsgProtocol.cpp, line 176

what's worse is the mail isn't getting sent.

I'll do some debugging.
now I'm not seeing this, but I swear I was.

if I waited long enough, I get the "sending message failed" alert, and the
compose window would come back.  it seemed long enough where something could
have timed out.

perhaps the smtp server was down this morning, and that exposed the problem?
cc esther, change qa contact
QA Contact: esther → sheelar
I just saw this again.

hopefully someone else will see it too.
see bug 72628.  It covers the "blocking the UI" issue....
I'm not sure if this is the same bug or not, but i haven't been able to send
messages at all since the March 14 or 16 builds. Mozilla completely freezes and
it never unfreezes (even after an hour). The last lines in my console when i do
this are as follows:

   SendMessage from XUL
   GenericSendMessage from XUL
   Identity = [nsIMsgIdentity: id1]
   attachments =

Mail is unusable for me until this is fixed.


Sorry, i forgot to mention my platform, which is Linux.
*** Bug 72628 has been marked as a duplicate of this bug. ***
*** Bug 73460 has been marked as a duplicate of this bug. ***
Yes, I think it may depend on the server state.  I've seen it where the message
appears to have been sent and then a long time later, I get the sending failed
dialog appear.

Perhaps we can test this out by using our test mail server such as "parp" to
bring down the smtp server right after the send.   Sheela - do you know how to
do that?
I'm running build 2001072503 (i.e. fairly recent :) on Windows 2000 and have the
exact same problem as Leston Buell (it gets to 'Connecting to server...', but no
further). I get the same stuff on the console, and this is not due to the mail
server being down, since (for me) the SMTP server *is* the IMAP server, and I
can get my mail fine.

A week or so ago, using 0.8.1, I was having a slightly different problem, which
still resulted in the mail not being sent. What would happen is this; I click
send, the status chages to something like 'Sending mail...' then a few moments
later (only about 15-30 seconds) I get a dialog saying there was an error from
the SMTP server mentioning something (sorry about the vagueness) about the
recipient's address being malformed/invalid (and perhaps something about
'transportation', as well).

And as Leston said, mail is unusable for me until this is resolved.
I think this (if this can be confirmed by one or two others) needs to be changed
to all OS's, not just Linux.
Seth,
Do you still see this problem now. I remember verifying a bug which fixed
blocking the UI while sending. Is this problem seen more so when the server is
down? 
changing QA contact from Sheela to Gregg
QA Contact: sheelar → meehansqa
I just came across this problem.  I have been using Mozilla 1.2b successfully
since it was released, but just today, I chose to send a mail message and the UI
stopped responding.  I checked top, and Mozilla's memory usage began increasing
steadily.  I've quit and restarted 1.2b three times and received the same
response.  The mail would never be sent, the UI would hang, and memory usage
would continue to increase.

I am currently using 1.1, and I have been able to send mail without problems so
far.  Both versions of Mozilla are using the same user configurations.

I am running Linux, and Mozilla does not seem to print anything to the console
when this error occurs.
Using 1.2b on Win98 too i just cannot send any mail.
I've got 5 pop3 accounts.
The problem is i can't save the e-mail too (ui hangs)
Workarround found : 
1. uninstall 1.2b & reboot
2. rename files history.dat, panacea.dat, localstore.rdf (dont't kwow if thios
helps) in the Application Data/default/....... directory 
3. re-install 1.0 & reboot
4. test e-mail send : yes ! it works fine !!
5. uninstall 1.0 & reboot
6. re-install 1.2b & reboot
--> seems to work again
I'm experiencing this bug as well.  Running WinME with Mozilla version 1.2.1.  I
don't feel like attempting the uninstall-reinstall fun listed above, but I did
try to delete each of the files listed (individually) and none of them brought
back my ability to send mail.
Okay, I just followed Ludovic Cheron's instructions above because I felt the
need to actually send e-mail again and it worked.  However, I did have issues
with the spell-checker.  I would crash when I was trying to send the test
message in version 1.0.1.  I noticed that I had two spell checking related DLL's
in my Mozilla.org\Mozilla\Components folder: spellchecker.dll & spellchk.dll.  I
deleted them and the crash went away in 1.0.1.  Then I updated (following the
above instructions) to 1.2.1 again and reinstalled the spellchecker and
everything seems happy again.

My curiosity wants to ask other people who are experiencing this bug as to
whether they have the spellchecker installed, and what's more, do you have both
DLL's if you're having this problem?  (Post uninstall-reinstall process I only
have spellchk.dll.  However I do have another machine running Mozilla 1.2.1 with
the spell checker installed and it has both DLL's as well and has yet to run
into this problem....)

Just a thought.
I take back my previous hypothosis.  My new (less than a day old and less than 3
e-mails sent) install of 1.2.1 is locking up again and I only have the one
spellchecker DLL.
I am having the same problem as James Ross. I have Windows XP Pro and whenever I
send/reply/forward it will get to the send dialog and then hang. It just sits
there. And the progress bar will move for about 15 seconds, and then it stops
and the program (any part of it, not just the Mail program) ceases to respond.
Here is my story: I use Mozilla heavily since summer. I upgraded to 1.3a a few
weeks ago. I have a notebook (Win XP) and a desktop (Win2K) computer and I
synchronize their data regularily. That means: I usually work on the desktop,
but occasionally copy everything to the notebook and continue to work on the
notebook. Then I move everything back to the desktop. I used ProfileManager to
point to the same data and preferences on both computers. This system worked
well in Summer.
Now I have the same symptom (ui freezes when attempting to send mail), but only
on my notebook. Surfing and downloading new mail works fine on both computers.
Besides the Mozilla version there were some more changes since summer:
- The notebook is new
- OS on notebook now Win XP (was Win98)
- I now acces Internet using an "SMC barricade" router (previously using some
PPPoE driver from my access provider)
I just made another test. The bug is clearly there. I synchronized all data back
to my desktop. Then I start Mozilla on the desktop. There I can see the mails
which I received when the data was on the notebook. From the desktop I can send
a mail without problem. Then I close Mozilla, sync back to the notebook, start
Moz there: I can see the sent message in the Sent folder, I can receive
messages. But as soon as I want to send another message: Moz locks, the
ventilator starts to work because Moz is using 99% of CPU, and I can only kill
the mozilla.exe process.
I suggest to mark this bug 
1. as "All platforms" because not only on Linux.
2. as duplicate or related to #145913 because in
my case the problem stopped to occur after I set "Use secure SMTP" to "never".
And on my notebook there was a Norton Antivirus running.

I've never had any setting except "NEVER" in the "Use secure SMTP" area.

On further notice.  I installed a post 1.3a (a week before this post's Nightly
Build probably) and did not experience this problem anymore.
I also have ran into this problem:

1. Hitting the "Send" button in a mail message caused mozilla to freeze
2. In a web page file-upload field, hitting the "browse" button (to find the
file on my local hard disk) also caused mozilla to freeze

The freeze was accompanied by a 100% CPU usage spike as reported by gkrellm.

My system:
Pentium III 1Gig
RedHat linux 7.3 (Valhalla) with custom 2.4.20 kernel with preempt and
lock-break patches
Mozilla 1.2.1 installed from RPMs

I have included the result of running strace on the command "mozilla -compose".
The strace clearly shows the problem, a repeat of this call "read(27, "",
8192)" at the end.  Tracing up the logfile, filehandle 27 is the result of
opening open("/home/mina/.mozilla/default/pp4cupac.slt/XUL.mfasl",
O_RDONLY|O_LARGEFILE)

Based on this info, I managed to fix my crashes by:
1. Renaming my .mozilla directory to .mozilla.old
2. Running mozilla and let it setup a new .mozilla directory, setup a dummy
mail account - sending worked okay
3. Rename .mozilla directory to .mozilla.new , restore .mozilla.old back to
.mozilla
4. Copy the XUL.mfast file from .mozilla.new (working) to .mozilla, overriding
existing copy
5. Problem fixed. Sending mail now works

I'm not exactly sure what the file XUL.mfast does, or why it would become
corrupt causing mozilla to crash, or why a brand-new version created by a new
profile seems to work, or why copying the new version over the old version
fixes the problem without affecting anything else (all my settings are
intact.).. However, whatever works...

I have in posession both the old non-functional XUL.mfasl and the new working
XUL.mfasl which I'd be willing to share with one of the developers if it'd help
you guys debug what's going on.

Best of luck to everyone with this problem.. Lack of the ability to send mail
is definately a huge issue IMO.

 - Mina Naguib
Attachment #115193 - Attachment mime type: text/plain → application/x-gzip
As a follow-up to my comment #23

I've encountered this problem (again) on my machine at work:
Linux RedHat 7.2 with 2.4.20 kernel
Intel Pentium III 600Mhz
256 Megs memory

The symptoms were the exact same as I described in my previous post, however,
I've discovered a quick(er) fix than what I outlined in my previous post.

There's no need to move the .mozilla directory etc..  I've found out that simply
deleting the XUL.mfasl file will fix the problem, and mozilla will recreate it
next time it starts.  And AFAIK there are no side effects, except that the
problem is fixed.

Mina Naguib
My system (1.2.1 on WinMe) has started experiencing this problem overnight.
Mozilla just freezes in the process of sending mail and has to be
ctrl+alt+del'd. In the absence of a workaround this renders the Mail program
useless.
Possible WinMe workaround to consider.

1. Close Mozilla.
2. Rename XUL.mfl as XULold.mfl, or whatever.
3. Restart Mozilla.

Mozilla re-creates XUL.mfl and Mail appears to resume normal functioning.
Removing XUL.mfl and having mozilla re-cre re-create XUL.mfl does not work for me.

This bug has pretty much compromised my ability to get anything done!

Does the alpha of the next version fix this?
Product: MailNews → Core
Seth do you still see this?  See comment 11
QA Contact: meehansqa → backend
Seth, still see this?  question in comment 11.
Assignee: mscott → nobody
Tuukka, ever see this on linux?
I've been asked to add a comment here by Wayne Mery, because I'm using Linux (Mandrake 10.1 followed by Mandriva 2007). I also use (dual boot) Win98SE

On Linux, as far as I can remember, I've not seen this problem in SM 1.0.6 to 1.1.9 (so far).

Even on Win98SE, where I progressed from NN 0.9 to 3.01, NC 2.5 to 4.74, NS 6.0 and 7.2 to Moz 1.6 and 1.7 then SM, I cannot remember sending mail hogging the CPU.

So, maybe, this bug was fixed somewhere between Moz 1.2.1 and Moz 1.6.

I don't recall ever seeing this the last 2-3 years on windows.

Mark meh@NOSPAMwinfirst.com says "I've never experienced the problem mentioned in the bug. I use both Linux and Windows/2000. I've been using Seamonkey since 1.0.2."  Thanks Mark.

=> WFM
Status: NEW → RESOLVED
Closed: 16 years ago
Resolution: --- → WORKSFORME
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: