Closed
Bug 48510
Opened 25 years ago
Closed 25 years ago
assertion if get PickleSecurityStatus before connection shutdown
Categories
(Core :: Security: PSM, defect, P3)
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.
Reporter | ||
Updated•25 years ago
|
Assignee | ||
Comment 2•25 years ago
|
||
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.
Reporter | ||
Comment 3•25 years ago
|
||
I am working on verifying and attaching a new patch with the conflicts resolved.
Assignee | ||
Comment 4•25 years ago
|
||
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 ;-)
Reporter | ||
Comment 5•25 years ago
|
||
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.
Reporter | ||
Comment 6•25 years ago
|
||
My test case is no longer crashing, I suspect the timing has changed.
Assignee | ||
Comment 7•25 years ago
|
||
Removing [nsbeta3+] statys since this no longer happens. Will investigate once
again if ther problem comes up again.
Whiteboard: [nsbeta3+]
Reporter | ||
Comment 11•25 years ago
|
||
This bug is no longer relevant.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•