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.
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.
Assignee: nobody → kengert
Component: Libraries → Security: PSM
Product: NSS → Core
QA Contact: libraries
Version: unspecified → Trunk
Summary: SECMOD_Shutdown fails because secmod_PrivateModuleCount is nonzero → reference leak of object from NSS
I have no extensions, but the cycle collector landed recently, maybe it leaks.
(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...
Neil, does the patch for bug 379582 also fix this problem?
(In reply to comment #5) >Neil, does the patch for bug 379582 also fix this problem? Yes, it does.
Status: NEW → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 379582
You need to log in before you can comment on or make changes to this bug.