637123 - 64-bit crash with NVIDIA Network Access Manager @ RtlpWaitOnCriticalSection | nvlsp64.dll

Status: RESOLVED INCOMPLETE

(Plugins Graveyard :: Nvidia ActiveArmor, defect)

Description

[Scoobidiver (away)]

It is a new crash signature that first appeared in 4.0b12pre/20110206.
With combined signatures, it is #1 top crasher in today's build.

Signature	ntdll.dll@0x4c8f4
UUID	786e9fab-078c-4de2-a9e6-c7ae72110227
Time 	2011-02-27 01:27:31.256430
Uptime	3176
Last Crash	3178 seconds (53.0 minutes) before submission
Install Age	4381 seconds (1.2 hours) since version was first installed.
Product	Firefox
Version	4.0b13pre
Build ID	20110226030201
Branch	2.0
OS	Windows NT
OS Version	6.1.7600
CPU	amd64
CPU Info	family 16 model 2 stepping 3
Crash Reason	EXCEPTION_ACCESS_VIOLATION_WRITE
Crash Address	0x24
App Notes 	AdapterVendorID: 10de, AdapterDeviceID: 0402, AdapterDriverVersion: 8.17.11.9745

Frame 	Module 	Signature [Expand] 	Source
0 	ntdll.dll 	ntdll.dll@0x4c8f4 	
1 	nvLsp64.dll 	nvLsp64.dll@0x36b1 	
2 	nvLsp64.dll 	nvLsp64.dll@0x6e2f 	
3 	nvLsp64.dll 	nvLsp64.dll@0x53e67 	
4 	ntdll.dll 	ntdll.dll@0x4c821 	
5 	nvLsp64.dll 	nvLsp64.dll@0x91ab 	
6 	ws2_32.dll 	ws2_32.dll@0x1abf 	
7 	nvLsp64.dll 	nvLsp64.dll@0x5520f 	
8 	ws2_32.dll 	ws2_32.dll@0x16a3 	
9 	ws2_32.dll 	ws2_32.dll@0x1cac 	
10 	ws2_32.dll 	ws2_32.dll@0x362f 	
11 	ws2_32.dll 	ws2_32.dll@0x739d 	
12 	ws2_32.dll 	ws2_32.dll@0x4b29 	
13 	ntdll.dll 	ntdll.dll@0xdf68 	
14 	nspr4.dll 	PR_MD_SEND 	nsprpub/pr/src/md/windows/w95sock.c:357
15 	ws2_32.dll 	ws2_32.dll@0x3331 	
16 	nspr4.dll 	PR_AssertCurrentThreadOwnsLock 	nsprpub/pr/src/threads/combined/prulock.c:404
17 	xul.dll 	nsCOMPtr_base::~nsCOMPtr_base 	obj-firefox/dist/include/nsAutoPtr.h:969
18 	KERNELBASE.dll 	KERNELBASE.dll@0x10ab 	
19 	xul.dll 	nsCOMPtr_base::~nsCOMPtr_base 	obj-firefox/dist/include/nsAutoPtr.h:969
20 	ws2_32.dll 	ws2_32.dll@0x2d27 	
21 	nspr4.dll 	PR_Unlock 	nsprpub/pr/src/threads/combined/prulock.c:347
22 	nspr4.dll 	PR_GetAddrInfoByName 	nsprpub/pr/src/misc/prnetdb.c:2079
23 	xul.dll 	nsHostResolver::ThreadFunc 	netwerk/dns/nsHostResolver.cpp:888
24 	nspr4.dll 	PR_NativeRunThread 	nsprpub/pr/src/threads/combined/pruthr.c:426
25 	nspr4.dll 	pr_root 	nsprpub/pr/src/md/windows/w95thred.c:122
26 	mozcrt19.dll 	_callthreadstartex 	obj-firefox/memory/jemalloc/crtsrc/threadex.c:348
27 	mozcrt19.dll 	_threadstartex 	obj-firefox/memory/jemalloc/crtsrc/threadex.c:326
28 	kernel32.dll 	kernel32.dll@0x1f56c 	
29 	ntdll.dll 	ntdll.dll@0x32cc0 	
30 	kernel32.dll 	kernel32.dll@0x9921f 	
31 	kernel32.dll 	kernel32.dll@0x9921f 	

More reports at:
https://crash-stats.mozilla.com/report/list?product=Firefox&range_value=4&range_unit=weeks&signature=ntdll.dll%400x4c8f4
https://crash-stats.mozilla.com/report/list?product=Firefox&range_value=4&range_unit=weeks&signature=ntdll.dll%400x4e4b4

Comment 1

[Matthias Versen [:Matti]]

This looks like that this is caused by the removed LSP blocking (bug 636088)

Comment 2

[Scoobidiver (away)]

> This looks like that this is caused by the removed LSP blocking (bug 636088)
It can explain the spike in crashes from 4.0b13pre/20110226.

There are also problems in Google Chrome: http://www.google.com/support/chrome/bin/static.py?page=known_issues.cs&&hl=en

Comment 3

[Matthias Versen [:Matti]]

and this is basically bug 527540 (we don't have LSP blocking in Gecko1.9.2)
Couldn't we change the LSP blocking in a blacklist for known broken LSPs ?

Comment 4

[Robert Strong (they/them - no direct email)]

Attachment: add nvlsp64.dll to nsWindowsDllBlocklist.h

Comment 5

[Robert Strong (they/them - no direct email)]

From the crash reports I see the following versions of nvLsp64.dll:
2.2.0.7305
2.2.0.7313
2.2.0.7316

Comment 6

[Scoobidiver (away)]

64-bit crashes are not 2.0 blockers.

Comment 7

[Kyle Huey (Exited; not receiving bugmail, old account, do not use)]

Please let drivers make that decision.

I'm not sure whether 'CPU' is what the binary was compiled for or what it running on.

Comment 8

[Makoto Kato [:m_kato]]

(In reply to comment #7)
> Please let drivers make that decision.
> 
> I'm not sure whether 'CPU' is what the binary was compiled for or what it
> running on.

CPU in crash report is binary format type.  So all crash is Windows x64 package..

And, block list on x64 build doesn't support yet.  If you add a entry into list for x64, it doesn't work until bug 604302 is fixed.

Comment 9

[Benjamin Smedberg]

As I understand the bug, it only occurs in 64-bit builds of Firefox, which we are not releasing. Please renominate if I am incorrect.

And khuey, drivers made this decision a long time ago, scoobidiver is merely helping.

Comment 10

[Benjamin Smedberg]

Comment on attachment 515549 [details] [diff] [review]
add nvlsp64.dll to nsWindowsDllBlocklist.h

I don't think we should land win64 blocklisting until we actually have official betas with which to gauge crashiness. The population is just too small to matter now.

Comment 11

[Robert Strong (they/them - no direct email)]

agreed

Comment 12

[timeless]

We're now tracking such bugs. This doesn't mean it's something we can fix, merely something we hope to be able to point vendors to so they can investigate. This is an automated message.

Comment 13

[Benjamin Smedberg]

Closing old bugs in the Plugins component. We aren't going to track issues in 3rd-party plugins in the Mozilla bug tracker. In addition, support for NPAPI plugins will be removed at the end of this year; for more details see the post at https://blog.mozilla.org/futurereleases/2015/10/08/npapi-plugins-in-firefox/

If there is a serious bug in Firefox, it needs to be filed in the "Core" product, "Plug-Ins" component.