Bug 1668593 Comment 0 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Original comment by
on 
Crash report: https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:
```
0 Security DERDecodeSeqContentInit 
1 Security parseX501NameContent 
2 Security SecCertificateCopySubjectSummary 
3 keychain-pkcs11.dylib keychain-pkcs11.dylib@0x5e92 
4 libnss3.dylib PK11_InitToken security/nss/lib/pk11wrap/pk11slot.c:1267
5 libnss3.dylib nssSlot_Refresh security/nss/lib/pk11wrap/dev3hack.c:238
6 libnss3.dylib nssSlot_IsTokenPresent security/nss/lib/dev/devslot.c:243
7 libnss3.dylib pk11_IsPresentCertLoad.llvm.17085532109926444036 security/nss/lib/pk11wrap/pk11slot.c:1603
8 XUL mozilla::psm::IsCertBuiltInRoot security/certverifier/CertVerifier.cpp:207
9 XUL nsNSSCertificate::GetIsBuiltInRoot security/manager/ssl/nsNSSCertificate.cpp:167
```
The crash is happening in a third part library, however I am seeing various crashes with the similar call stack. Such s [this](https://crash-stats.mozilla.org/report/index/6edb751b-db39-47eb-9076-4ad730200929) and [this](https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930).
Revision 1 by
on 
Crash report: https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:
```
0 Security DERDecodeSeqContentInit 
1 Security parseX501NameContent 
2 Security SecCertificateCopySubjectSummary 
3 keychain-pkcs11.dylib keychain-pkcs11.dylib@0x5e92 
4 libnss3.dylib PK11_InitToken security/nss/lib/pk11wrap/pk11slot.c:1267
5 libnss3.dylib nssSlot_Refresh security/nss/lib/pk11wrap/dev3hack.c:238
6 libnss3.dylib nssSlot_IsTokenPresent security/nss/lib/dev/devslot.c:243
7 libnss3.dylib pk11_IsPresentCertLoad.llvm.17085532109926444036 security/nss/lib/pk11wrap/pk11slot.c:1603
8 XUL mozilla::psm::IsCertBuiltInRoot security/certverifier/CertVerifier.cpp:207
9 XUL nsNSSCertificate::GetIsBuiltInRoot security/manager/ssl/nsNSSCertificate.cpp:167
```
The crash is happening in a third part library, however I am seeing various crashes with the similar call stack. Such as [this](https://crash-stats.mozilla.org/report/index/6edb751b-db39-47eb-9076-4ad730200929) and [this](https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930).
Revision 2 by
on 
Crash report: https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930

Reason: EXC_BAD_ACCESS / KERN_INVALID_ADDRESS

Top 10 frames of crashing thread:
```
0 Security DERDecodeSeqContentInit 
1 Security parseX501NameContent 
2 Security SecCertificateCopySubjectSummary 
3 keychain-pkcs11.dylib keychain-pkcs11.dylib@0x5e92 
4 libnss3.dylib PK11_InitToken security/nss/lib/pk11wrap/pk11slot.c:1267
5 libnss3.dylib nssSlot_Refresh security/nss/lib/pk11wrap/dev3hack.c:238
6 libnss3.dylib nssSlot_IsTokenPresent security/nss/lib/dev/devslot.c:243
7 libnss3.dylib pk11_IsPresentCertLoad.llvm.17085532109926444036 security/nss/lib/pk11wrap/pk11slot.c:1603
8 XUL mozilla::psm::IsCertBuiltInRoot security/certverifier/CertVerifier.cpp:207
9 XUL nsNSSCertificate::GetIsBuiltInRoot security/manager/ssl/nsNSSCertificate.cpp:167
```

The crash is happening in a third party library, however, I am seeing various crashes with a similar call stack. Such as [this](https://crash-stats.mozilla.org/report/index/6edb751b-db39-47eb-9076-4ad730200929) and [this](https://crash-stats.mozilla.org/report/index/6b9ccdfc-8d61-477b-8e75-845710200930).

Back to Bug 1668593 Comment 0