Closed Bug 117911 Opened 23 years ago Closed 23 years ago

[core] attempt to open msg cores MailNews crash

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
critical

Tracking

(Not tracked)

VERIFIED INVALID

People

(Reporter: garretta, Assigned: sspitzer)

References

()

Details

(Keywords: crash)

Hello -- received the msg from co-workers. Attempt to open msg (from Inbox) causes immediate crash. bld #2002010103 http://www.garretta.com/msg-crash2.txt Talkback ID's: TB1181666X, TB1181435X, TB1181212E
small note: in order to submit issue, I had to open msg in Communicator v4.79 (wintel), view source, select all/copy, save contents to new text file, and post (ie. can't provide .eml file). -GA
Keywords: crash
confirmed with different bld #2002010303. I moved problematic msg to IMAP sub-folder (via Communicator v4.79). The same file still causes immediate core with new Mozilla build referenced above. Talkback ID# TB1212013Q Thx-GA
verify problem still present with build #2002010703. Talkback ID# TB1352911E.
Summary: [core] attempt to open msg crash Mail/News crash → [core] attempt to open msg cores MailNews crash
verify issue present with build #2002010803. Also, verified new profile doesn't affect results -- still crash.
talkback ID for last crash-test on build #2002010803: talkback TB1466663E
verify crash with #2002011403. Talkback ID# TB1663262H. -GA
received another msg that evokes same behavior (ie. mailnews crash) ref -- http://www.garretta.com/msg-crash3.txt Note: this msg not a result of "send page" from broswer (like first example). This message is signed by S/MIME. This is latest build: #2002012103
verify core with latest build: 2002012304. Talkback ID # TB2061639X. Check: http://www.garretta.com/msg-crash2.txt
new msg produces crash for latest daily of 0.9.8 (#2002012806). http://www.garretta.com/msg-crash4.txt This problem has occurred about three/fours times now where Mail/News can't open a msg and immediately cores. I know two suspect messages where composed with Netscape Communicator and were signed (s/mime) -- ref 'msg-crash3.txt' and 'msg-crash4.txt'.
sorry -- talkback ID for latest update: #TB2252292M. (core with #2002012806)
determine I'm describing two problems herre -- one msg-type Cores Mail/News, second type (s/mime) cores Mail/News when PSM has password set (ie. normal). When PSM doesn't have password protection, signed messages open w/o core. Closing this bug, and opening two separate. -GA
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → INVALID
0x021602e1 nsProxyObjectManager::GetProxyForObject [d:\builds\seamonkey\mozilla\xpcom\proxy\src\nsProxyObjectManager.cpp, line 225] PK11PasswordPrompt [d:\builds\seamonkey\mozilla\security\manager\ssl\src\nsNSSCallbacks.cpp, line 169] PK11_DoPassword() PK11_DoPassword() PK11_Authenticate() PK11_GetBestSlotMultiple() PK11_GetBestSlot() PK11_VerifyRecover() VFY_CreateContext() VFY_CreateContext() VFY_VerifyData() CERT_VerifyCertChain() NSS_CMSSignerInfo_VerifyCertificate() NSS_CMSSignedData_VerifySignerInfo() MimeMultCMS_generate [d:\builds\seamonkey\mozilla\mailnews\mime\src\mimemcms.cpp, line 411]
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.