Closed Bug 541293 Opened 15 years ago Closed 6 years ago

sharp rise in Firefox Crashes [@ strlen | PR_DestroyLock ] mid Jan 2k10

Categories

(Core :: General, defect)

x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED WONTFIX

People

(Reporter: chofmann, Unassigned)

Details

(Keywords: crash, Whiteboard: [crashkill])

Crash Data

6-10 crash in early jan 2010, then ramp in the last few days.

20100113-crashdata 20 PR_DestroyLock
20100114-crashdata 26 PR_DestroyLock
20100115-crashdata 54 PR_DestroyLock
20100116-crashdata 169 PR_DestroyLock
20100117-crashdata 278 PR_DestroyLock
20100118-crashdata 277 PR_DestroyLock
20100119-crashdata 326 PR_DestroyLock
20100120-crashdata 372 PR_DestroyLock

currently ranking  #16 in first day of 3.6 data.

several users claim possible virus but none have been able to isolate

this keeps happening and i have no bugs on my comp i scaned with 3 differnt scanners and found nothing i can only go to one page and thats it after that it takes about a 2hrs to load and this is not a lie i sat fir 2hrs waiting for a page to load

would only let me start firefox in save mode 

this crash has happened to me often since my Firefox update... I am clueless as to what is going on. It mostly happens when I attempt to open an (https:// as opposed to http://) 

closes after a few minutes, and says it is running after it automatically closes, no other web browsers are working either

anitmalware is killling me. FF keep shutting down then won't restart because it says it's still running. I do ctl-alt-del and kill FF then restart and FF says OOPS this is embarassing..." Still trying to get avg to load up but is shuts down too. Getting LOTS of redirection in links and searches when FF is working but not all the time. I had to delete all I could on IE becase this "virus" is making IE the default browser. I have to keep going into FF and fixing that and SOMETIMES theres more

Working on clearing a trojan. Firefox is the only residual problem: stays resident and crashes even when minimized. Same behavior with 3.5.7 & RC 6. I believe it is related to bugs I acquired on this test PC. Oddly enough..no problem with IE8. 

stack looks like

http://crash-stats.mozilla.com/report/index/88ccbcbd-623a-4822-a8e9-6b6bb2100117

Frame  	Module  	Signature [Expand]  	Source
0 	ntdll.dll 	strlen 	
1 	nspr4.dll 	PR_DestroyLock 	
2 	xul.dll 	nsSocketOutputStream::Write 	netwerk/base/src/nsSocketTransport2.cpp:576
3 	xul.dll 	nsHttpConnection::OnReadSegment 	netwerk/protocol/http/src/nsHttpConnection.cpp:539
4 	xul.dll 	nsHttpTransaction::ReadRequestSegment 	netwerk/protocol/http/src/nsHttpTransaction.cpp:433
5 	xul.dll 	nsStringInputStream::ReadSegments 	xpcom/io/nsStringStream.cpp:276
6 	xul.dll 	nsHttpTransaction::ReadSegments 	netwerk/protocol/http/src/nsHttpTransaction.cpp:458
7 	xul.dll 	nsHttpConnection::OnSocketWritable 	netwerk/protocol/http/src/nsHttpConnection.cpp:574
8 	xul.dll 	nsHttpConnection::OnOutputStreamReady 	netwerk/protocol/http/src/nsHttpConnection.cpp:785
9 	xul.dll 	nsSocketOutputStream::OnSocketReady 	netwerk/base/src/nsSocketTransport2.cpp:515
10 	xul.dll 	nsSocketTransport::OnSocketReady 	netwerk/base/src/nsSocketTransport2.cpp:1564
11 	xul.dll 	nsSocketTransportService::DoPollIteration 	netwerk/base/src/nsSocketTransportService2.cpp:674
12 	xul.dll 	nsSocketTransportService::OnProcessNextEvent 	netwerk/base/src/nsSocketTransportService2.cpp:538
13 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:508
14 	xul.dll 	NS_ProcessPendingEvents_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:200
15 	xul.dll 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:250
16 	xul.dll 	nsSocketTransportService::Run 	netwerk/base/src/nsSocketTransportService2.cpp:581
17 	xul.dll 	nsThread::ProcessNextEvent 	xpcom/threads/nsThread.cpp:527
18 	xul.dll 	NS_ProcessNextEvent_P 	obj-firefox/xpcom/build/nsThreadUtils.cpp:250
19 	xul.dll 	nsThread::ThreadFunc 	xpcom/threads/nsThread.cpp:254
20 	nspr4.dll 	_PR_NativeRunThread 	nsprpub/pr/src/threads/combined/pruthr.c:426
21 	nspr4.dll 	pr_root 	nsprpub/pr/src/md/windows/w95thred.c:122
22 	mozcrt19.dll 	_callthreadstartex 	obj-firefox/memory/jemalloc/crtsrc/threadex.c:348
23 	mozcrt19.dll 	_threadstartex 	obj-firefox/memory/jemalloc/crtsrc/threadex.c:326
24 	kernel32.dll 	BaseThreadStart


more reports at

http://crash-stats.mozilla.com/report/list?range_value=2&range_unit=weeks&signature=strlen%20|%20PR_DestroyLock&version=Firefox%3A3.6
signature list
 367 strlen | PR_DestroyLock
   5 PR_DestroyLock

Correlation to startup
372 total crashes for PR_DestroyLock on 20100120-crashdata.csv
55 start up crashes inside 3 minutes

os breakdown
247     0.663978        Windows NT5.1.2600 Service Pack 3
114     0.306452        Windows NT5.1.2600 Service Pack 2
5       0.0134409       Windows NT6.0.6001 Service Pack 1
3       0.00806452      Mac OS X10.4.11 8S165
2       0.00537634      Windows NT6.0.6002 Service Pack 2
1       0.00268817      Windows NT6.0.6000

 247 strlen | PR_DestroyLock Windows NT 5.1.2600 Service Pack 3
 113 strlen | PR_DestroyLock Windows NT 5.1.2600 Service Pack 2
   4 strlen | PR_DestroyLock Windows NT 6.0.6001 Service Pack 1
   3 PR_DestroyLock Mac OS X 10.4.11 8S165
   2 strlen | PR_DestroyLock Windows NT 6.0.6002 Service Pack 2
   1 strlen | PR_DestroyLock Windows NT 6.0.6000
   1 PR_DestroyLock Windows NT 6.0.6001 Service Pack 1
   1 PR_DestroyLock Windows NT 5.1.2600 Service Pack 2

seems to stretch across a wide range of firefox versions, but mostly appears in latest updates.   users also seem to be trying firefox 3.6 as a possible fix, then getting disappointed that they still see the crash, or hit the problem just after update and think its related to installation of 3.6.
higher than normal correlation in a few .dll's like

    100% (50/50) vs.  16% (3706/22797) wzcsapi.dll
        - Wireless Zero Configuration service API from Microsoft
     30% (15/50) vs.   1% (265/22797) SynTPFcs.dll
         Progressive Touch version 7.5.0 by Synaptics, Inc..
     70% (35/50) vs.  10% (2324/22797) dot3dlg.dll

and a few others like over in bug 538724 which had a ramp up earlier in Jan. starting Jan 5.
Crash Signature: [@ strlen | PR_DestroyLock ]
Closing because no crash reported since 12 weeks.
Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.