Mozilla crashes regularly (100%) after downloading mail from POP account

RESOLVED EXPIRED

Status

--
critical
RESOLVED EXPIRED
14 years ago
10 years ago

People

(Reporter: lutzkonermann, Assigned: sspitzer)

Tracking

({crash})

Trunk
PowerPC
Mac OS X
crash

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113

Mozilla would crash 100% for sure after downloading, completely receiving and
storing mail from a POP3 mail account. Afer restart, mail will be in the inbox
but left on the mail server as well. Same happens with Netscape 7.1 (sharing the
same user profile...!). I suspect a problem in communicating "download complete"
to the POP3 server. Netscape 4.5 running in Classic under OS 9.2 (and thus not
sharing the same profile...?!) works seamlessly.

Reproducible: Always
Steps to Reproduce:
1. Restart Mozilla
2. "Get mail" from POP3 account


Actual Results:  
 Mozilla crashes "unexpectedly" (no error code in OSX)

Expected Results:  
Well, apart from Mozilla not crashing, the mail should not only have been
received (which actually happens) but also deleted from the POP3 server (which
does not happen).

Comment 1

14 years ago
Does the bug also happen with a current build (Mozilla 1.7.3 or 1.8a4)?
(Reporter)

Comment 2

14 years ago
(In reply to comment #1)
> Does the bug also happen with a current build (Mozilla 1.7.3 or 1.8a4)?

Yes. I just installed 1.7.3 and tested it. There's no such bug with Thunderbird
which I also just installed!

Comment 3

14 years ago
what about 1.8a4? it should be similar to thunderbird... if it works there, we
can mark this works for me...
(Reporter)

Comment 4

14 years ago
(In reply to comment #3)
> what about 1.8a4? it should be similar to thunderbird... if it works there, we
> can mark this works for me...

1.8a4 crashes...

Comment 5

14 years ago
ok, one more thing - can you try a recent nightly trunk seamonkey build, i.e., a
build closer to 1.8a5? that'll help us determine if this has been fixed on the
trunk at all
(Reporter)

Comment 6

14 years ago
(In reply to comment #5)
> ok, one more thing - can you try a recent nightly trunk seamonkey build, i.e., a
> build closer to 1.8a5? that'll help us determine if this has been fixed on the
> trunk at all

Hi, well, this sounds like you well know of the problem...?! Hmmm, while
downloading this night's latest MAC built - before installing that and maybe
reporting another crash, is there any specific built that you could point me to
and want me to test...? 

Bests, Lutz

Comment 7

14 years ago
the fact that it works in thunderbird means that it's most likely fixed -
mozilla seamonkey and thunderbird share the same backend code, which is most
likely where the crash is. The latest trunk mozilla build is here:

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

thx for trying this...
(Reporter)

Comment 8

14 years ago
(In reply to comment #7)
> the fact that it works in thunderbird means that it's most likely fixed -
> mozilla seamonkey and thunderbird share the same backend code, which is most
> likely where the crash is. The latest trunk mozilla build is here:
> 
> http://ftp.mozilla.org/pub/mozilla.org/mozilla/nightly/latest-trunk/
> 
> thx for trying this...

That's the one I just tried: crash...

Comment 9

14 years ago
darn, did a talkback report get filed?

generating a pop3 protocol log might help:

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

(Reporter)

Comment 10

14 years ago
While we're at it: How would I "import" my mail folders in thunderbird? Since it
looks like I'm better off with a Thunderbird/Firefox combo. Unless there's a
corrupted file hidden in my mail folders...
(Reporter)

Comment 11

14 years ago
(In reply to comment #9)
> darn, did a talkback report get filed?
> 
> generating a pop3 protocol log might help:
> 
> http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html#pop3
> 
> 

Yes, I filed a Talkback report on the last two crashes. Shall I still try
creating the POP3 log?

Comment 12

14 years ago
I can't get to talkback right now, so a protocol log might be helpful in the
meantime...
(Reporter)

Comment 13

14 years ago
(In reply to comment #12)
> I can't get to talkback right now, so a protocol log might be helpful in the
> meantime...

I just created the log command in TextEdit. But the TextEdit file would not be
dropable onto the Mozilla icon. However, the text clip would (it would highlight
the icon before dropping). After one more crash I can't find the log file in the
"package"'s MacOS folder, though...

Here's my text clip:
ARGS:-mail
ENV:NSPR_LOG_MODULES=POP3:5
ENV:NSPR_LOG_FILE=pop3log.doc

Updated

14 years ago
Keywords: crash
Lutz Konermann, do you use manual "Run Filter on folder"?
If yes, your problem is possibly same as mine, Bug 266905.
I experienced symptom you described in comment #0, crash on new mail receive,
many times.
So I stopped using "Run Filter on folder". If used, I restarted Mozilla.  
Then I am not experincing crash.
(Reporter)

Comment 15

14 years ago
(In reply to comment #14)
> Lutz Konermann, do you use manual "Run Filter on folder"?
> If yes, your problem is possibly same as mine, Bug 266905.
> I experienced symptom you described in comment #0, crash on new mail receive,
> many times.
> So I stopped using "Run Filter on folder". If used, I restarted Mozilla.  
> Then I am not experincing crash.

Thanks for your hint, Wada, but no, I've never used that feature. :-(

Comment 16

14 years ago
reporter: can you copy the talkback incident id here?
(Reporter)

Comment 17

14 years ago
(In reply to comment #16)
> reporter: can you copy the talkback incident id here?

Hmm, couldn't find the Talkback application on my harddrive... (?!) But here's
the contents of the ini file:
HistorySettings = 3, 10, 100
SeenIntro = 1
WantUpdates = 0
UserEmailAddress = "lutzkonermann@compuserve.com"
LocalKey = 79EC263A71
RandomPool =
ABF7A9EAF2C74D60417A76A8083E4AD5EE3422FCFB4DA59D4689D97EC582BD629658D101B0709EFF58B966BC70BA9F75C0B43376E5EEDF058A56287AA5B0B9F209DDD1F2DFC8B8F6E14B1C0E03B0DD1713F221A697F8181761E77636F51254F9D19919EC4937CAB4764A9015506F84B394216B8CC8BE6AB83382497E754501B7
(In comment #0)
> Same happens with Netscape 7.1 (sharing the same user profile...!).
> Netscape 4.5 running in Classic under OS 9.2
> (and thus not sharing the same profile...?!) works seamlessly.
(In comment #1)
> There's no such bug with Thunderbird which I also just installed!

Lutz Konermann, I can't understand why you haven't tested with new profile yet.
All most all "Release Notes" describes on it and following is example of 1.7.3.
> Before you install
> (snip) 
> If you have Netscape 6 or 7 installed
> Do NOT share profiles between Mozilla and Netscape 6 or 7.

Will Mozilla with newly created profile/account work?

If your problem occurs even with new profile, your problem can be guessed server
and Mozilla(not Thundebird) communication related problem or mail data related
problem only when Mozilla mail&News.

Comment 19

14 years ago
I am having the same problem (it just started today).  System is RedHat 9 with
Mozilla 1.7.2 (Seamonkey).  I tried the recommended turning off of all filters.
 Mail still crashes.  I tried Thunderbird and it crashes as well.  Thunderbird
is using pop3 to my Exchange server (I captured the exchange using ethereal, the
last message is a DELE 41 followed by Exchange sending +OK, then Thunderbird dies.).

I also tried deleting cache, deleting possible bad mails (using Evolution),
and removing my XUL file.....

How can one debug this?  Is there a way to turn on some type of logging? 

Comment 20

14 years ago
This is on Linux/PC, not Mac, but it has the same result.

I just tried Thunderbird with a new profile, not imported profile,
and it works fine.  There seems to be a problem with my mail folders.

How can you fix them?

Comment 21

14 years ago
a few things in no particular order.
1. does crash reporter not open up? normally it should, the report from that
should work
2. we could try using gdb ./thunderbird-bin eventually
3. http://www.mozilla.org/quality/mailnews/mail-troubleshoot.html
open Terminal.app
cd /Applications/Thunderbird.app/Content/MacOS/
export NSPR_LOG_MODULES=pop3:5
export NSPR_LOG_FILE=/tmp/pop3.log
./thunderbird-bin

for linux users, the steps are about the same, although to run and get a stack
trace you really need a talkback build, or your own cvs build (w/ --enable-debug
or --enable-debugger-info-modules)
Product: MailNews → Core
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/
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.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
Product: Core → MailNews Core
You need to log in before you can comment on or make changes to this bug.