Seamonkey trunk builds after 4/05 crashes when try to start mail&news(with currently using profile and account definition). Several POP3 accounts and several news accounts are active, and "Check for new messages at startup" and "Check for new messages every NN minute" is enabled for some POP3 accounts. Talkback IDs : 1. TB17423529G (Build ID: 2006040509) 2. TB17325586E (Build ID: 2006040710) 3. TB17325707H (Build ID: 2006040710) (Note: NSPR log of NSPR_LOG_MODILES=all:5 is available.) 4. TB17325707H (Build ID: TB17423556M) If "CANCEL" is replied to Dr. Watson's dialog for cancel application, Seamonkey can continue to work even after the crash, although failure occurs while trying to connnect to POP3 server and further POP3 access is impossible. NSPR log of above (3.) is obtained by this "CANCEL" reply. If NSPR log is required for problem analysis, let me know, please. This crash started to occur from 4/05 build. Last non-crash build is 4/03 build. Note: 4/04 build won't start with -ProfileManager. Profile selection panel is started, but "Start" nor "Exit" button on profile selection panel doesn't works. "X" button at upper right corner is required to close profile slection panel. Since crash problem of Bug 333534 also started to occur from 4/05 build and still occurs with 4/10 build, root cause of this bug and Bug 333534 may be same.

User Agent(When Build ID: 2006041010) : Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a1) Gecko/20060410 SeaMonkey/1.5a Add-On's etc. : LiveHTTPHeaders(latest 0.12) is installed. No other extentions is installed. ( http://livehttpheaders.mozdev.org/index.html ) Theme: Standard "Modern". Virtical 3 pane layout is used. Other specials of my environment: Pipelining is enabled. A POP3 account, to which Seamonkey mail&news accesses on start-up, is APOP.

(Correction of comment #0, sorry for spam) 4. TB17423556M (Build ID: 2006040810)

Bug 211260 has relation to this bug?

Similar issue to Bug 332348?

This problem(and Bug 333534 also) started to occur from 4/04 build(2006040411, Win32 ZIP build). "Not start" problem on 4/04 build was: 1. If last used profile is choosed at profile selection, Seamonkey won't start. 2. When another profle is choosed, Seamonkey starts normally, but profile selection panel was not closed, and stayed to open even after shutdoewn of main Seamonkey windows. 3. Profile selection panel can not be closed by "Exit" button. Clickng of upper right corner of the panel is required to close profile selection panel. So, if wanted profile is choosed after choosing another profile and start&stop Seamonkey, start up of Semonkey was possible, and same crash of this bug was observed on 2006040211 trunk build. TalkbackID : TB17564915G (Build ID: 2006040411) Chaninging to XPCOM because crash in XPCOM module, to request first analysys of crash.

Incident ID: 17564915 Stack Signature PL_DHashTableOperate b8af08e5 Product ID MozillaTrunk Build ID 2006040411 Trigger Time 2006-04-14 01:08:55.0 Platform Win32 Operating System Windows NT 5.0 build 2195 Module xpcom_core.dll + (0000131d) URL visited User Comments Since Last Crash 394 sec Total Uptime 394 sec Trigger Reason Access violation Source File, Line No. c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/build/pldhash.c, line 492 Stack Trace PL_DHashTableOperate [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/build/pldhash.c, line 492] nsCStringHashSetSuper::GetEntry [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/xpcom/ds/nsHashSets.cpp, line 43] nsSSLIOLayerAddToSocket [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp, line 2552] nsSSLIOLayerNewSocket [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp, line 1399] nsTLSSocketProvider::NewSocket [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/security/manager/ssl/src/nsTLSSocketProvider.cpp, line 73] nsSocketTransport::BuildSocket [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 988] nsSocketTransport::InitiateSocket [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1090] nsSocketTransport::OnSocketEvent [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1406] nsMultiMixedConv::AddRef [c:/builds/tinderbox/MozillaTrunk/WINNT_5.0_Clobber/mozilla/netwerk/streamconv/converters/nsMultiMixedConv.cpp, line 387] 0x81088b56

Might be caused by checkins from bug 111384, I will start analyzing this bug, and reassign if it turns out it's something else.

Talback with Seamonkey trunk 2006050310(Win32 ZIP build,Win-2K) : TB18280596E No Seamonkey trunk nightly builds newer than 4/03 for my daily use during this one month - mail&news is not usable. It's new world record of term of crash or critical problem for me. It was two weeks since my first use of Mozilla M17 till 2006/04/03. Is there any relation to Bug 333534? (Both started to occur on 4/04 build, and still occurs) What's wrong or special in my environment? MS Win 2K? NETBIOS over TCP and file share with SMB? Keiro personal firewall? Avast!? Japanese IME? Mail directry on D: drive instead of Profile directry on C: drive? Profile initially created when Mozilla 1.4 and updated/upgraded/migrated by many many trunk nightlies? POP3 server of APOP is used? prefs.js entries for extentions which is not used currently? (No meanig for Seamonkey, but invalid entries, so it may affect on Seamonkey...)

Talkback ID with 2006050310: TB18313609H (that was for Bug 333534. sorry for spam)

*** Bug 338767 has been marked as a duplicate of this bug. ***

DUP'ed Bug 338767 is for same crash when trying 'check for updates' when Firefox 1.8 Branch(20060521 BonEcho/2.0a2) on MS Win XP. kaie, do we need to get and present additional data such as NSPR log or prefs.js?

i forgot to present a talkback id for the branch on bug 338767 http://talkback-public.mozilla.org/search/start.jsp?search=2&type=iid&id=TB18813948Z looks like the same as

Incident ID: 18813948 Stack Signature PL_DHashTableOperate b189ed28 Product ID Firefox2 Build ID 2006051604 Trigger Time 2006-05-17 17:59:31.0 Platform Win32 Operating System Windows NT 5.1 build 2600 Module xpcom_core.dll + (0000131e) URL visited User Comments Since Last Crash 6 sec Total Uptime 439 sec Trigger Reason Access violation Source File, Line No. c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/build/pldhash.c, line 547 Stack Trace PL_DHashTableOperate [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/build/pldhash.c, line 547] nsCStringHashSetSuper::Init [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/xpcom/ds/nsHashSets.cpp, line 44] nsNSSEventGetUIEventQueue [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsNSSEvent.cpp, line 63] nsContinueDespiteCertError [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsNSSIOLayer.cpp, line 1547] nsPK11Token::destructorSafeDestroyNSSReference [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/security/manager/ssl/src/nsPK11TokenDB.cpp, line 138] nsSocketTransport::IsAlive [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/base/src/nsSocketTransport2.cpp, line 1749] nsCookie::nsCookie [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/cookie/src/nsCookie.h, line 99] nsFileChannel::~nsFileChannel [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/netwerk/protocol/file/src/nsFileChannel.h, line 72] nsXPCWrappedJSClass::CheckForException [c:/builds/tinderbox/Fx-Mozilla1.8/WINNT_5.2_Depend/mozilla/js/src/xpconnect/src/xpcwrappedjsclass.cpp, line 959] 0x81088b56

I am not able to reproduce this crash. I wish I could. I tried the help/check for updates on windows - does not crash for me.

(In reply to comment #14) > I am not able to reproduce this crash. Can CPU or memory size(shortage) have relation? My note is Cerelon 600MHz/128MB/10GB HDD - Poorman's PC :-)

I was able to test on a 733 Mhz i586 machine with crusoe processor. 384 MB ram. It worked fine, no crash at all. I could try to disassemble that machine and remove some ram... Not sure if that's really the cause. xtc4uall: are you using a low end computer?

I've found what's wrong when my environment: Cause of my crash was "TLS, if avail" of "Server Settings"/"Secutiry Settings"/ "Use Secure Connection" of POP3 accounts. Changing to "Never" was workaround of my crash. Test result with Seamonkey trunk 2006-02-26 build(ZIP,Win-2K): (1-A) POP3, "TLS, if avail" : Get Msg => Crash (1-B) SMTP, "TLS, if avail" : Send => Crash (2-A) POP3, "Never" : Get Msg => No Crash. No problem in mail download. (2-B) SMTP, "Never" : Send => No Crash. No problem in mail sending. Note: Crash during shutdown(Bug 333534) still remains.

Correction. Sorry for spam. - Tested with trunk 2006-05-26 build. (NOT 02-26)

i wouldn't consider calling my box 'low-end': pentium4 2,6 GHz (with HT) 1 GB infineon pc3200 ram win xp sr-2 (german) moreover i wonder now why 'my' bug got duped since it's triggered by software update and happens on brach _and_ trunk unlike this bug .... nevertheless i will test both builds in a vmware session if this is reproducable there too. will it make sense to post more talkback ids ?

Same crash was easily be re-created without 'TLS, if avail' of Mail&News. Start Seamonkey(Browser only), and go http(s)://bugzilla.mozilla.org/query.cgi This crash occured with all of 4/04 build, some builds after 4/04 and 6/05 build. Talkback ID : TB19589072Y (6/05 build, Win32-ZIP, on Win-2K)

Kaie, can we get an update on this?

i am still unable to reproduce, but it is on my list of things i want to work on for ff 2

changing summary(add description on crash when 'https:' access)

WADA, do you use the "Ad Muncher" program on your computer? See bug 342646.

i can verifiy admuncher being the cause of my mentioned crashes here and in 342646

err, i meant https://bugzilla.mozilla.org/show_bug.cgi?id=338767 sorry for the spam

(In reply to comment #24) > WADA, do you use the "Ad Muncher" program on your computer? See bug 342646. No. I connect to provider(KDDI) directly. But via. VDSL modem(router type, NAT is used) and fiber, and I use Keiro Personal Firewall. Do I need to take NSPR log when crash(4/04 build or later)? Do I need to take NSPR log when no problem(3/29 build or 4/03 build)? Note: crash when access to https:bugzilla.mozilla.org occurs even when newly created profile/clean program library(unziped directry of win32 ZIP build).

(In addition to comment #27) Packet filetering is enabled in my VDSL modem(default setting of the VDSL modem).

I killed Keiro Personal Firewall, then no crash! (I'm writing this comment with 7/13 build, without Keiro Personal Firewall) I also think this crash is similar to "Ad Muncher" case.

I upgraded "Keiro Personal Firewall"(free/basic version) to 4.3.246 from 4.2.2 today, then crash problem on 4/04 trunk build to 7/13 trunk build disappeared. (both bug 333540 and bug 333534 did't occur.) When KPF 4.2.2, no asking for permission of connection to 127.0.0.1(loopback), but when Sunbelt KPF 4.3.246, dialog for permission of connection to 127.0.0.1 appeared in addition to dialog for usual access to an IP address. > (New dialog for permission by Sunbelt KPF 4.3.246) > Direction: outgoing > Local Point: 0.0.0.0, port 1228 > Adapter: N/A > Remote Point: localhost [127.0.0.1], port 1227 > Protocol: TCP This indicates that design change was made for 127.0.0.1/loopback by KPF 4.2.3(2005/12/15) or KPF 4.3.246(2006/5/22). (Note: "Keiro Personal Firewall" was aquired by "Sunbelt Software" from "Kerio Technologies" in Dec. 2005, and KPF 4.2.2 is last version by "Kerio Technologies".) Kai Engert, which is better? (a) Close as WORKSFORME (b) Close as DUP of bug 342646

I have a security question here for people who use KPF or Ad Muncher. When you install those products, do they add a certificate to your browser's (or email client's) list of trusted certificate authorities? Or do they instruct you to add such a cert for use with their products? If you're not sure, you could email a copy of your cert8.db file to me, as an attachment. (Cert8.db contains no personal private keys of yours, only public key certificates for CAs or web sites or email correspondents.)

I am working on a fix after having tested with AdMuncher installed, as reported in bug 342646. Let's retest this bug with your Keiro firewall, after bug 342646 has been marked fixed.

*** Bug 333534 has been marked as a duplicate of this bug. ***

(In reply to comment #32) > Let's retest this bug with your Keiro firewall, after bug 342646 has been > marked fixed. As I wrote in comment #30, I already upgraded KPF then problem has gone. And old KPF is not available any more because KPF was bought by "Sunbelt Software". So sorry but I can't re-create the problem any more. Closing as DUP of bug 342646. kaie, thanks for your effort. *** This bug has been marked as a duplicate of 342646 ***