Closed Bug 863740 Opened 11 years ago Closed 8 years ago

crash in npjp2.dll@0xca1f with Java SE 7 Update 21 & 25

Categories

(Plugins Graveyard :: Java (Oracle), defect)

x86
Windows 7
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: scoobidiver, Unassigned)

Details

(Keywords: crash)

Crash Data

It's likely bug 828889 with an address shift.
It's currently #281 browser crasher in 20.0.1 with a rising tendency.

Signature 	npjp2.dll@0xca1f More Reports Search
UUID	4aa2f452-4e5f-4a60-b0f5-bb49d2130419
Date Processed	2013-04-19 07:42:13
Uptime	43
Install Age	2.0 days since version was first installed.
Install Time	2013-04-17 08:06:31
Product	Firefox
Version	20.0.1
Build ID	20130409194949
Release Channel	release
OS	Windows NT
OS Version	6.1.7601 Service Pack 1
Build Architecture	x86
Build Architecture Info	GenuineIntel family 6 model 30 stepping 5
Crash Reason	EXCEPTION_ACCESS_VIOLATION_READ
Crash Address	0x1
User Comments	Formula1 Live Timing
App Notes 	
AdapterVendorID: 0x10de, AdapterDeviceID: 0x0df0, AdapterSubsysID: 00000000, AdapterDriverVersion: 8.17.12.6672
D2D? D2D+ DWrite? DWrite+ D3D10 Layers? D3D10 Layers+ 
Processor Notes 	sp-processor03.phx1.mozilla.com_21394:2012; non-integer value of "SecondsSinceLastCrash"; exploitability tool failed: 127
EMCheckCompatibility	True
Adapter Vendor ID	0x10de
Adapter Device ID	0x0df0
Total Virtual Memory	4294836224
Available Virtual Memory	3594784768
System Memory Use Percentage	43
Available Page File	9627697152
Available Physical Memory	3630866432

Bugzilla - Report this bug in Firefox, Core, Plug-Ins, or Toolkit
Crashing Thread
Frame 	Module 	Signature 	Source
0 	npjp2.dll 	npjp2.dll@0xca1f 	
1 	npjp2.dll 	npjp2.dll@0xcbad 	
2 	npjp2.dll 	npjp2.dll@0xc2bc 	
3 	msvcr100.dll 	_threadstartex 	f:\dd\vctools\crt_bld\self_x86\crt\src\threadex.c:292
4 	kernel32.dll 	BaseThreadInitThunk 	
5 	ntdll.dll 	__RtlUserThreadStart 	
6 	ntdll.dll 	_RtlUserThreadStart 	

npjp2.dll 	10.21.2.11 	7B2EC43661A84375BD9E86E9C2CDC6F31 	npjp2.pdb

More reports at:
https://crash-stats.mozilla.com/report/list?signature=npjp2.dll%400xca1f
Any URLs standing out here?
Keywords: needURLs
Is there better stack trace for npjp2.dll so we can debug further ?
The only way we can get a better trace is by getting the symbols for npjp2.dll. I'll follow up with you on that; I think we have a way we can do that.
It's now #20 top crasher in 20.0.1.
Keywords: topcrash
The latest Java version is also affected based on correlations:
    100% (135/135) vs.   1% (531/39054) java.dll
         17% (23/135) vs.   0% (97/39054) 7.0.210.11
         24% (32/135) vs.   0% (126/39054) 7.0.250.16
         59% (80/135) vs.   1% (256/39054) 7.0.250.17
Summary: crash in npjp2.dll@0xca1f with Java SE 7 Update 21 → crash in npjp2.dll@0xca1f with Java SE 7 Update 21 & 25
I see java.dll in the above comment.

Is that crash now in npjp2.dll or java.dll ?
(In reply to Thomas Ng from comment #7)
> I see java.dll in the above comment.
> Is that crash now in npjp2.dll or java.dll ?
It's an extract from correlations per module but the stack trace of comment 0 hasn't changed. See bp-709d1b5e-3bd4-419b-b5b9-95b1d2130701 for instance with Java SE7 U25.
This is now #14 on 22 release. There's also a npjp2.dll@0xc2bc signature rising, which is similar to this one. Do we have a non-CTP-blocked Java version out there again?
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #9)
> There's also a npjp2.dll@0xc2bc signature rising, which is similar to this one.

npjp2.dll@0xcc2d and npjp2.dll@0xcc26 as well.
(In reply to Robert Kaiser (:kairo@mozilla.com) from comment #9)
> This is now #14 on 22 release. There's also a npjp2.dll@0xc2bc signature
> rising, which is similar to this one. Do we have a non-CTP-blocked Java
> version out there again?

I think 7U25 is not CTP-blocked and the current block applies to <=7U24.
When we're blocking the latest version of Java this doesn't appear in top crash.  It's not currently in top crash criteria.
Keywords: topcrash
Bug#912895(created by me Sachin, on Sept-5-2013) has been closed as duplicate of this bug#863740(created on Apr-19 by Scoobidiver).   Plese note it may be a different bug in following respects->

# we found it occurring only in windows server 2008 (64bit) , windows 2008 R2 server only
# its not occurring in windows7
# its found to be occurring(ie. Firefox is crashing) on accessing our applet in our web-application using firefox 21 (or 22 or 23 ) the VERY FIRST TIME after Machine restart. After the crash, when we restart firefox, and do the same step (i.e. access our web-application using firefox) then it doesn't crash.  To get crash-scenario, we have to restart the Machine. 

Please revalidate if Bug#912895 is duplicate of this bug
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.
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.