41704 - ab sync crashes: the problem is the PSM bits have timebombed

Status: VERIFIED DUPLICATE of bug 41490

(SeaMonkey :: MailNews: Address Book & Contacts, defect, P3)

Description

[(not reading, please use [e-mail] instead)]

the problem is the PSM has timebombed.  there is already another bug out there
on that.  

we crash because ab sync tries to do a https connection, and an expired PSM
causes us to crash.

this is just to let everyone know about the crasher.  nothing for to do here.

Here's the stack trace:

#0  0x40561111 in __kill ()
#1  0x402a3f7b in raise (sig=6) at signals.c:63
#2  0x40562447 in abort () at ../sysdeps/generic/abort.c:88
#3  0x40262674 in PR_Assert (s=0x424f4d34 "PR_SUCCESS == rv", file=0x424f4d20
"nsPSMShimLayer.c", ln=87) at prlog.c:477
#4  0x424d8fdc in nsPSMShimGetSocket (unixSock=1) at nsPSMShimLayer.c:87
#5  0x42501cd8 in CMT_ControlConnect (mutex=0x424fac28, sockFuncs=0x424fac60) at
cmtinit.c:300
#6  0x424da92d in nsPSMComponent::GetControlConnection (this=0x8cca408,
_retval=0xbf7ff64c) at nsPSMComponent.cpp:418
#7  0x424ddb37 in nsSSLIOLayerConnect (fd=0x820b0b0, addr=0x8cc87bc, timeout=20)
at nsSSLIOLayer.cpp:101
#8  0x4025f283 in PR_Connect (fd=0x820b0b0, addr=0x8cc87bc, timeout=20) at
priometh.c:166
#9  0x40dc2330 in ?? () from
/builds/seth/seamonkey/ns/dist/bin/components/libnecko.so
#10 0x40dc19fe in ?? () from
/builds/seth/seamonkey/ns/dist/bin/components/libnecko.so
#11 0x40dc5f0b in ?? () from
/builds/seth/seamonkey/ns/dist/bin/components/libnecko.so
#12 0x40dc666e in ?? () from
/builds/seth/seamonkey/ns/dist/bin/components/libnecko.so
#13 0x40112337 in ?? () from /builds/seth/seamonkey/ns/dist/bin/libxpcom.so
#14 0x40286a2b in _pt_root (arg=0x81309b8) at ptthread.c:157
#15 0x402a1ce9 in pthread_start_thread (arg=0xbf7ffe7c) at manager.c:204

Comment 1

[(not reading, please use [e-mail] instead)]

internal netscape people:  see #41490 for details on how to get a working PSM.

Comment 2

[scottputterman]

marking as a dup of 41490


*** This bug has been marked as a duplicate of 41490 ***

Comment 3

[pmock]

Verified as a duplicate of bug 41490