Closed Bug 140747 Opened 23 years ago Closed 23 years ago

Mail crash on POP Account Retrieve from Empty Mailbox - M110B N700 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState]

Categories

(MailNews Core :: Networking: POP, defect)

x86
Windows 98
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME
mozilla1.2alpha

People

(Reporter: Oddee, Assigned: naving)

Details

(Keywords: crash, qawanted, topcrash-, Whiteboard: [need info])

Crash Data

This crash is reported on Talkback submission TB5698941G captured 4/28/02 10:37AM. This is on nightly Win32 Mozilla dated 4/27/02, and has occurred on previous nightly builds since RC1. I don't know whether or not this bug was present prior to RC1. This occurs on a Windows 98 machine *without* Internet Explorer (I suppose a Windows 95 machine without IE would be an equivalent test case) running AOL 6.0 for internet access. Procedure: Upon entering password for a POP account in the POP password dialog box for the first time (on _both_ a new Mozilla profile and a converted Netscape 4 profile) and checking the "Remember password" box, Mozilla crashes after clicking OK. The browser can be restarted and functions normally, however upon opening Mail again Mozilla crashes. The computer must be restarted for Mozilla Mail to not crash on open. Expected result: No crash
This is possibly an extension of this same bug. Mozilla crashes on Mail startup randomly after the given procedure is performed. It did not occur on the first Mail startup after restartign the computer, but on the 3rd startup of Mail. This was after sending the first message through SMTP with the password being remembered, shutting down Mozilla, and restarting it during the same Windows session. Starting mail again led directly to a crash after the chrome was painted. Talkback ID TB5700170K 4/28/02 11:25AM.
May be a dup of bug 74997?
An analysis of the Talkback data may yield some useful info. The subsequently reported crashing seems to be random, but the first testcase is consistently reproduceable. Perhaps there are new DLL's which the Win32 Mozilla requires that are not present on non-IE machines. A similar problem with non-IE machines was in bug 130614 , but that was a bookmark problem that caused crashing - but there is plenty of precedence for certain functions not working correctly on non-IE Windows machines.
Here's the stack trace: nsPop3Protocol::ProcessProtocolState [nsPop3Protocol.cpp, line 2845] nsMsgProtocol::OnDataAvailable [nsMsgProtocol.cpp, line 306] nsOnDataAvailableEvent::HandleEvent [nsStreamListenerProxy.cpp, line 202] PL_HandleEvent [plevent.c, line 597] PL_ProcessPendingEvents [plevent.c, line 530] _md_EventReceiverProc [plevent.c, line 1078]
Summary: Mail crash on POP Account password Entry → Mail crash on POP Account password Entry [@ nsPop3Protocol::ProcessProtocolState]
triaging
Assignee: mscott → naving
Component: Mail Back End → Networking - POP
QA Contact: gayatri → sheelar
Additional scenario for crashing Mail, I do not know whether or not the same bug is responsible. Talkback ID TB5754907K 4/29/02 9:14PM. Test case on the same system: Run Mozilla, and open mail. Retrive new mail, read, and close mail. Then open mail once more. This leads to an crash as soon as the Mail chrome finishes painting. An analysis of the Talkback build might give some info as to whether or not this should stay within the same bug or be opened anew.
I think this may have nothing to do with pop. Could you try imap/news? I think it will crash there also.
I believe I have figured out the source of this problem. Whenever Mozilla checks for mail on my POP account, and no new mail is on the server, Mail crashes. This happens for two separate situations: one, if Mail is opened, and nothing is on the server. Two, if Mail is opened, new mail is retrieved, and Mail remains open until the next auto check (10 minutes) and finds nothing new on the server.
This is crashing for Mozilla 1.0 RC2. Adding crash keywords and nominating. Here is the latest from Talkback on this crash for M1RC2: Count Offset Real Signature [ 7 MSVCRT.DLL + 0x2678 (0x78002678) 6f93a5d9 - nsPop3Protocol::ProcessProtocolState ] Crash date range: 2002-05-11 to 2002-05-13 Min/Max Seconds since last crash: 9 - 38491 Min/Max Runtime: 1612 - 49691 Keyword List : Count Platform List 7 Windows NT 5.0 build 2195 Count Build Id List 7 2002051008 No of Unique Users 2 Stack trace(Frame) MSVCRT.DLL + 0x2678 (0x78002678) nsPop3Protocol::ProcessProtocolState [d:\builds\seamonkey\mozilla\mailnews\local\src\nsPop3Protocol.cpp line 2861] nsMsgProtocol::OnDataAvailable [d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgProtocol.cpp line 306] nsOnDataAvailableEvent::HandleEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamListenerProxy.cpp line 203] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 597] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 530] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 1078] nsAppShellService::Run [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp line 451] main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1473] main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1809] WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1827] WinMainCRTStartup() KERNEL32.DLL + 0xd326 (0x77e8d326) ============================================================ Count Offset Real Signature [ 3 MSVCRT.DLL + 0x4a16 (0x78004a16) 0a5db173 - nsPop3Protocol::ProcessProtocolState ] Crash date range: 2002-05-12 to 2002-05-13 Min/Max Seconds since last crash: 18 - 4922 Min/Max Runtime: 4922 - 5844 Keyword List : Count Platform List 3 Windows NT 5.0 build 2195 Count Build Id List 3 2002051008 No of Unique Users 1 Stack trace(Frame) MSVCRT.DLL + 0x4a16 (0x78004a16) nsPop3Protocol::ProcessProtocolState [d:\builds\seamonkey\mozilla\mailnews\local\src\nsPop3Protocol.cpp line 2845] nsMsgProtocol::OnDataAvailable [d:\builds\seamonkey\mozilla\mailnews\base\util\nsMsgProtocol.cpp line 306] nsOnDataAvailableEvent::HandleEvent [d:\builds\seamonkey\mozilla\netwerk\base\src\nsStreamListenerProxy.cpp line 203] PL_HandleEvent [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 597] PL_ProcessPendingEvents [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 530] _md_EventReceiverProc [d:\builds\seamonkey\mozilla\xpcom\threads\plevent.c line 1078] nsAppShellService::Run [d:\builds\seamonkey\mozilla\xpfe\appshell\src\nsAppShellService.cpp line 451] main1 [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1473] main [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1809] WinMain [d:\builds\seamonkey\mozilla\xpfe\bootstrap\nsAppRunner.cpp line 1827] WinMainCRTStartup() KERNEL32.DLL + 0x7903 (0x77e77903) Not a lot of users, but a few are crashing consistently (probably due to the unique environment required to see the crash as noted in this bug). Added qawanted keyword to see if we can get this reproduced in-house.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: Mail crash on POP Account password Entry [@ nsPop3Protocol::ProcessProtocolState] → Mail crash on POP Account password Entry - M1RC2 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState]
Sheela, can you try to reproduce this?
Whiteboard: [need info]
I followed the steps described by the reporter in his comments #8 also in his intial reporting. Testing done to try to reproduce this problem: Commercial branch build: 05-29-06 on win98 Create a new profile with a pop test account (Netscape pop server) Login prompt, enter password and checked remember password Did not change any default settings. Clicked on get messages to actually download them. Compose and send a message. Wait biff to fire at 10 minute interval Biff did go off and no crash apparently. Just found biff arrow at the account level. Waited for another 10 minutes without sending any mail. Biff did go off when there were no mail on the server to retrieve. I then changed the settings to auto download messages. Tired the two test cases were biff gets the new message from the server. And biff fires when there are no new messages to download. No crash. I also downloaded mozilla build RC2 and repeated the above scenarios as well. I was not able to reproduce this crash. Reporter, Is this crash consistent and can be reproduced by you still on recent builds?
Yes, this crash is consistent under the test case of checking mail on a POP account with no retrievable mail. It still occurs on RC3. You said you tried it under Windows 98, maybe a test under Windows 95 without IE would be reproduce this crash, as I'm using Win98 with IE removed, via 98lite. If you want, I can send in another talkback capture from RC3, as it is still occuring.
I have Windows ME and Mozilla 1.0 RC 3. I created an e-mail account to a pop server (road runner). I copied all the info from Outlook Express manually (because when I tried to import it, it put it under local folers and wouldn't let me get messages). I know I entered the passoword correctly (and I told it to remember it) and the first time, I got mail. But subsequent to that, whenever I ask to get messages, I get a message that reads "The PASS command did not succeed. Mail server pop-server.nycap.rr.com responded: Password failed for rgraham2" This loops until I kill the app.
Robert W Graham: The problem you are describing is similar to problem reported in bug 147872. Let us not get mixed up and loose track of the original problem reported here.
Discussed in Mail News bug meeting. Decided to minus this bug.
Keywords: nsbeta1nsbeta1-
Target Milestone: --- → mozilla1.2alpha
This problem still exists under Moz1.0 final. I've sent in another Talkback build in case anything has changed, ID TB7125177G datd 6/7/02 at 10:45PM Eastern time.
Changing summary now that the test case has been narrowed down, from password entry to retrieve from empty POP mailbox
Summary: Mail crash on POP Account password Entry - M1RC2 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState] → Mail crash on POP Account Retrieve from Empty Mailbox - M1RC2 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState]
Talkback reports show only the reporter has submitted incidents with this signature in the last ten days on any release. -> topcrash-
Keywords: topcrashtopcrash-
Some new information. This bug still exists on the latest nightly, and I submitted a Talkback on it. However, I have another situation in which this crash does not happen on the same computer. I just added a new POP account, so now I have 2, and when I check the new account and its empty (no new mail), there is no crash. However, when I check the old account and its empty, there is still a crash.
Re-tested bug on Mozilla 1.1beta Win32, still exists. Attempting to retrieve mail from the primary POP account while it is empty yields a crash (latest submitted talkback ID# TB8637882Q), but retrieving mail from the secondary POP account when it is empty does not yield a crash.
Mozilla 1.1b (build 2002072204) running under Linux crashes every time I try to retrieve e-mail to my newly created and empty account. There is no e-mail to retrieve from the server-- I was just trying to test the mail account settings.
Has anyone been able to reproduce this with a more recent MozillaTrunk or with any Mozilla milestone/release after Mozilla 1.0? If so, can you post your Talkback ID.
QA Contact: sheelar → esther
I haven't seen any crashes like this in recent MozillaTrunk or in Mozilla 1.2 Beta...so marking this worksforme. If anyone is able to reproduce, please post your Talkback ID and feel free to reopen.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Updating summary with M110B and N700 since Mozilla 1.1 Beta and Netscape 7 were the last 2 major releases to show this crash.
Summary: Mail crash on POP Account Retrieve from Empty Mailbox - M1RC2 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState] → Mail crash on POP Account Retrieve from Empty Mailbox - M110B N700 [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState]
Product: MailNews → Core
Product: Core → MailNews Core
Crash Signature: [@ MSVCRT.DLL - nsPop3Protocol::ProcessProtocolState]
You need to log in before you can comment on or make changes to this bug.