Closed Bug 48510 Opened 25 years ago Closed 25 years ago

assertion if get PickleSecurityStatus before connection shutdown

Categories

(Core :: Security: PSM, defect, P3)

1.0 Branch
x86
Linux
defect

Tracking

()

VERIFIED WONTFIX

People

(Reporter: jgmyers, Assigned: javi)

References

Details

(Whiteboard: [nsbeta3-])

This is related to bug 46739. Running with the patch attached to bug 31982, I frequently get asserts on sslconn.c:262. One thread is trying to destroy the data connection while another is still in SSM_SSLDataServiceThread on the connection. This happens most, but not all of the time, so timing likely has something to do with this.
Blocks: 31982
Keywords: nsbeta3
Putting on nsbeta2 radar
Whiteboard: [nsbeta3+]
jgmyers: Can you check in your patch to some branch you create? The diff's way to large to apply by hand and there won't be any errors if I do a cvs up -j instead of manually patching my tree from your diff.
I am working on verifying and attaching a new patch with the conflicts resolved.
My point is that your patch is so big that applying it by hand will surely lead to an error on my part. If you create a branch that was used only as a vehicle for deilvering your patch to my tree, that would reduce the chance of me mis-applying the patch. It's a simple cvs tag -b ;-)
Once an updated patch is created, you should apply it with the "patch -p0" command, not by hand. Creating a branch is a nontrivial undertaking since there are changes to netwerk and conflicts are freqent.
My test case is no longer crashing, I suspect the timing has changed.
Removing [nsbeta3+] statys since this no longer happens. Will investigate once again if ther problem comes up again.
Whiteboard: [nsbeta3+]
marking nsbeta3- per Javi's comment
Whiteboard: [nsbeta3-]
Changing QA contact to nitinp
QA Contact: lord → nitinp
Mass reassigning nitinp's bugs to me.
QA Contact: nitinp → junruh
This bug is no longer relevant.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
Verified wontfix based on jgmyers's comment.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Version: psm1.2 → 1.0 Branch
You need to log in before you can comment on or make changes to this bug.