188812 - crash while sending an e-mail

Status: RESOLVED WORKSFORME

(MailNews Core :: Networking: SMTP, defect)

Description

[Jozef Riha]

User-Agent:       Mozilla/5.0 (X11; U; Linux i686; sk-SK; rv:1.2.1) Gecko/20021130
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; sk-SK; rv:1.2.1) Gecko/20021130

crashes when I try to send an e-mail. really ugly :(

Reproducible: Sometimes

Steps to Reproduce:
1. click on "reply" button
2. write an email message
3. click on Send

Actual Results:  
4. top shows mozilla takes 97 - 100 cpu time
5. after a while mozilla goes down
sometimes it crashes even without replying to an existing e-mail.

Expected Results:  
send it and stay alive! :)

Comment 1

[Matthias Versen [:Matti]]

that sounds like a hang/freeze and not like a crash.

Reporter:
Can you please close Mozilla, RENAME the file xul.mfasl and retrz it ?
Please don't delete that file, we need it..

Comment 2

[Andrew Hagen]

Reporter, please try the above troubleshooting step.

If it doesn't work, please download the latest nightly trunk build and install
it. Does that solve the problem?

Comment 3

[Andrew Hagen]

Reporter, to troubleshoot this problem, please follow these steps. When you
reply, make sure to include your operating system version and the Mozilla build
ID. The Mozilla build ID is located in the Mozilla title bar. If the problem is
sovled, please indicate what step solved it.

1. Make sure that the test machine you're running is in good condition. On
Windows 9x, run scandisk. On Windows NT/2000/XP, error-check the drives. On
*nix, check for filesystem errors. Furthermore, if you have an antivirus
program, make sure the antivirus definitions and program files are up to date.
Make sure you have recently scanned the system for viruses, and removed any you
find. Once this is complete, can you still reproduce the problem?

2. Download and install the latest trunk nightly build.  Running a nightly build
has a slight amount of risk involved. Back up your Mozilla data including your
bookmarks before proceeding. You can download the latest nightly build from
ftp://ftp.mozilla.org/pub/mozilla/nightly/latest . For example, for Windows,
download the file mozilla-win32-installer-sea.exe. Uninstall your current
Mozilla build. Make sure the new directory where you will install the new build
is completely empty, except for any plugins subdirectory. Install the nightly
build. Having done that, can you still reproduce the problem?

3. If it still fails, exit Mozilla. Go to your profile directory. Find the file
xul.mfl (or xul.mfasl on *nix). Rename it. Restart Mozilla. Does that solve the
problem?


Before following the next steps, create an SMTP log. Attach the SMTP log to this
bug. The steps for creating the log can be found here:

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


4. 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?

5. 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?

6. 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?

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

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

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

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

If none of these steps work, please attach an SMTP log. 

Comment 4

[Matthias Versen [:Matti]]

no response

Comment 5

[Jozef Riha]

feel free to close this bug report. somehow it is working now.. thanks anyways.
/joe/