366440 - reference leak of object from NSS

Status: RESOLVED DUPLICATE of bug 379582

(Core :: Security: PSM, defect)

Description

[[e-mail]]

Someone on IRC who doesn't like to use Bugzilla complained that SeaMonkey won't switch profiles. I was able to reproduce the issue in SeaMonkey 1.5a by opening a secure site and attempting to switch profile. What seems to be happening is that secmod_PrivateModuleCount is nonzero. This causes SECMOD_Shutdown to fail, which triggers nsNSSComponent to cancel the profile change.

Comment 1

[Nelson Bolyard (seldom reads bugmail)]

That means some code in SeaMonkey leaked a reference to an NSS object.  
Could even be an extension doing it.  Not an NSS fault.  
Can you reproduce this in a new "clean" profile (no extensions) ?

I'll retarget to PSM for now, but it may get retargetted again if it is 
found to be related to an extension, or if it is only reproducible in 
SeaMonkey.

Comment 2

[[e-mail]]

I have no extensions, but the cycle collector landed recently, maybe it leaks.

Comment 3

[Boris Zbarsky [:bzbarsky]]

Probably depends on bug 366578 being fixed before we can debug...

Comment 4

[[e-mail]]

(In reply to comment #3)
>Probably depends on bug 366578 being fixed before we can debug...
Sorry to bugspam, but my 17-hour-old build still asserts on shutdown...

Comment 5

[Nelson Bolyard (seldom reads bugmail)]

Neil, does the patch for bug 379582 also fix this problem?

Comment 6

[[e-mail]]

(In reply to comment #5)
>Neil, does the patch for bug 379582 also fix this problem?
Yes, it does.