Closed Bug 115927 Opened 23 years ago Closed 23 years ago

NSS3.4 / Crash when opening cert trust edit twice

Categories

(Core Graveyard :: Security: UI, defect, P1)

Other Branch
x86
Linux
defect

Tracking

(Not tracked)

VERIFIED FIXED
psm2.2

People

(Reporter: KaiE, Assigned: KaiE)

References

Details

Attachments

(1 file)

Open cert manager, authorities tab. Select any cert. Klick Edit to open the "edit trust" dialog. Within that, click cancel. Now click "edit" again. Actual result: crash The crash is triggered by: Assertion failure: module->refCount == 0, at pk11util.c:599 I talked to Bob, he confirmed that the assertion is correct. "If the module has not been destroyed, then it should still be holding a reference to a slot. If you are tripping overt this problem it means someone is freeing a reference to a slot that they did not own." Most likely this means, the PSM code has a bug somewhere.
This is not happening with 3.3.
Priority: -- → P1
Target Milestone: --- → 2.2
How do we get in the SECMOD_SlotDestroyModule() code by cancelling this dialog and then clicking on edit cert? The code that gets called is in nsCertOuliner::GetCertAtIndex(). ->kaie
Assignee: ssaux → kaie
Attached patch Suggested fixSplinter Review
Bob, do you think this patch is correct?
Yes, it looks correct. PK11_FindCertByIssuerAndSN should be returning a Reference to the slot. bob
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → FIXED
Patch checked in to tip of NSS. fixed
Blocks: 116334
Kai, looks like this problem still exists - at least on NT - even after I updated pk11cert.c. Happens when I open edit trust twice, or when I try to delete two certs one after the other in the same session...
Sorry - my mistake - I got it going for me now ..
Verified with the 1/7/02 trunk Linux build.
Status: RESOLVED → VERIFIED
Product: PSM → Core
Product: Core → Core Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: