Closed
Bug 176827
Opened 22 years ago
Closed 22 years ago
hang/spin when send message is pressed
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
VERIFIED
DUPLICATE
of bug 168516
People
(Reporter: allyn, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.2b) Gecko/20021016
this morning when i tried to send email (clicking send in the compose window)
mozilla hung. i found it spinning using the task manager with memory usage
increasing. i repeated this several times over several reboots.
(100% repeatability at that point).
i removed all of the msf files, let mozilla rebuild a few yet the problem
remained. looking through the mail&newsgrous account settings, i found a
similar hang when clicking on copies&folders. letting mozilla rebuild the
summary file for the Sent folder cured the problem.
so apparently the problem was a corrupt Sent msf file.
Reproducible: Didn't try
Steps to Reproduce:
1.
2.
3.
Expected Results:
shouldn't corrupt msf file causing sending mail to hang.
Comment 1•22 years ago
|
||
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2b) Gecko/20021016
Had same problem. Deleting sent.msf solved it for me.
I'm having this problem in trunk build 2002102704, on Linux Suse 8.0.
Will now try deleting sent.msf.
From the account I was trying to send on, I still can't send.
Tried the following:
1. Delete send.msf in same account sending from.
Then did send
2. Go to sent folder to re-build sent.msf
Then did send
3. Deleted sent.msf
4. Deleted inbox.msf
5. Inbox.msf rebuilt
Then did send.
5. Deleted every msf.
6. Inbox.msf of sending account re-created
Then did send.
For each send, could kill with sigterm. once had to use sigkill.
Have just had mozilla crash on me, after leaving mozilla hung for couple of
minutes.
Talkback ID: TB13373303E
Please mark this bug as critical.
It is not fixed by deleting/rebuilding sent.msf.
I can't use mail in this version, have dropped back to trunk 2002100108.
Please don't let this get into the final 1.2 release.
Comment 6•22 years ago
|
||
I have a similar report in bug 177986.
I confirm on build 28 oct (1.2b) on WinXP.
there seem to be other users reporting this!
thank you.
With my roll-back to the 2002100108 build, sending e-mail is definately working.
Assignee | ||
Comment 8•22 years ago
|
||
seems more a copy problem than a send one for me. After the send operation is
complete, we copy the message to the sent folder.
Navin, any idea?
Assignee | ||
Comment 9•22 years ago
|
||
Also, I forget to say that the build from October 16 is totally bogus. Reporter,
have you tried a more recent build?
Comment 10•22 years ago
|
||
I had the problem twice with 1.2b 16 oct (winxp) and 1 time with build 28 oct:
pressing the mail button (or doing ctrl-enter) hangs mozilla: high cpu load, non
responsive, forced quit.
I resolved the problem by downloading a mozilla build (very recent build, like 1
nov) and install it in *another* directory (zipped distribution!) and running
it. somehow, it fixed my problems. I restarted the 28oct build and I could send
mail again.
still, the fact remains I had 3 times this error last week, with 1.2b build 16
and 28 oct.
michael (see bug 177986, same problem)
Comment 11•22 years ago
|
||
If deleting XUL.mfasl (or similar depending on your system) fixes this (make
sure Mozilla is not running!), this is a dupe of bug 172547. If so, please mark
it as such.
pi
Comment 12•22 years ago
|
||
this bug report is a dupe of bug 177986, I think. bug 177986 has been resolved
for build 1.2. maybe time to change the status of this bug report?
cheers
M
Comment 13•22 years ago
|
||
oops, must be dupe of bug 172547 (not resolved)
Comment 14•22 years ago
|
||
Marking as dupe then.
pi
*** This bug has been marked as a duplicate of 168516 ***
Status: UNCONFIRMED → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•