Firefox 3.7a1 Crash [@ RtlEnterCriticalSection ]

RESOLVED DUPLICATE of bug 521849

Status

()

defect
RESOLVED DUPLICATE of bug 521849
10 years ago
8 years ago

People

(Reporter: chofmann, Assigned: kaie)

Tracking

({crash})

Trunk
x86
macOS
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

(crash signature)

#2 top crash in 3.7a1 data

new crash with signature RtlEnterCriticalSection but a different underlying problem than bug Bug 524921

http://crash-stats.mozilla.com/topcrasher/byversion/Firefox/3.7a1

http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=RtlEnterCriticalSection&version=Firefox%3A3.7a1

Frame      Module      Signature [Expand]      Source
0     ntdll.dll     RtlEnterCriticalSection     
1     nspr4.dll     PR_Lock     nsprpub/pr/src/threads/combined/prulock.c:233
2     xul.dll     nsAutoLock::nsAutoLock    
obj-firefox/dist/include/nsAutoLock.h:219
3     xul.dll     nsSSLIOLayerHelpers::isKnownAsIntolerantSite    
security/manager/ssl/src/nsNSSIOLayer.cpp:2230
4     xul.dll     nsSSLIOLayerSetOptions    
security/manager/ssl/src/nsNSSIOLayer.cpp:3501
5     xul.dll     nsNSSShutDownPreventionLock::~nsNSSShutDownPreventionLock    
security/manager/ssl/src/nsNSSShutDown.cpp:472
6     xul.dll     nsSSLIOLayerNewSocket    
security/manager/ssl/src/nsNSSIOLayer.cpp:2250
the crashes with this particular signature and stack seem to happen within 40 seconds of startup.
 	EXCEPTION_ACCESS_VIOLATION  	0x30

this is a null pointer crash which makes sense. i'll try to look into it if no one else does...
Keywords: crash
Looks like duplicate as bug 521849, but this one is specific to windows.  However I'm not sure if this is also FIPS related.

We should try to take the quick fix from that bug on m-c.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
Duplicate of bug: 521849
Crash Signature: [@ RtlEnterCriticalSection ]
You need to log in before you can comment on or make changes to this bug.