Closed Bug 702307 Opened 13 years ago Closed 1 year ago

PSM: Crash in SECOID_FindOID_Util

Categories

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

ARM
Android
defect

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: briansmith, Unassigned)

References

Details

(Keywords: crash, Whiteboard: [mobile-crash][native-crash][psm-backlog])

Crash Data

+++ This bug was initially created as a clone of Bug #517615 +++

My initial hunch is that bug 696551 is the cause.

(In reply to Nelson Bolyard (seldom reads bugmail) from bug 517615 comment 43)
> Of course, what really needs to be fixed is the non-NSS bug that held 
> onto a reference to an NSS object that caused the NSS shutdown to fail.  
> Even if NSS doesn't crash, if it cannot shutdown, then thereafter the 
> application is in an inconsistent security state..  The application 
> should not continue.  
> 
> For Firefox, the top priority should be to fix whatever code OUTSIDE of NSS 
> is holding a reference, thereby preventing NSS from shutting down.

(In reply to Naoki Hirata :nhirata from bug 517615 comment 46)
> Also occurred in Aurora (ffx 8 ) for Fennec 
> https://crash-stats.mozilla.com/report/
> list?range_value=7&range_unit=days&date=2011-09-
> 26%2008%3A00%3A00&signature=PL_HashTableLookupConst&version=Fennec%3A8.0a2

(In reply to Scoobidiver from bug 517615 comment 47)
> It's #5 top crasher in Fennec 8.0.

As Nelson said, this is almost definitely a bug in Gecko that triggers the buggy behavior in NSS. It will probably be faster to fix the Gecko bug than the NSS bug. In fact, although we are crashing in the same place as in bug 517615, it might be due to misuse of NSS instead of any NSS bug. Again, see bug 696551.
Changing summary so that bugmail threading isn't so confusing.
Summary: Crash in secoid code, trying to reinitialize after failed NSS shutdown [@ PL_HashTableLookupConst ] → PSM: Crash [@ PL_HashTableLookupConst ]
Keywords: topcrash
Depends on: 716345
Whiteboard: [mobile-crash] → [mobile-crash][native-crash]
Crash Signature: [@ PL_HashTableLookupConst ] → [@ PL_HashTableLookupConst ] [@ PL_HashTableLookupConst | SECOID_FindOID_Util]
Summary: PSM: Crash [@ PL_HashTableLookupConst ] → PSM: Crash in SECOID_FindOID_Util
Assignee: brian → nobody
Whiteboard: [mobile-crash][native-crash] → [mobile-crash][native-crash][psm-backlog]

Since the crash volume is low (less than 5 per week), the severity is downgraded to S3. Feel free to change it back if you think the bug is still critical.

For more information, please visit auto_nag documentation.

Severity: critical → S3

Closing because no crashes reported for 12 weeks.

Status: NEW → RESOLVED
Closed: 1 year ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.