Closed Bug 768002 Opened 11 years ago Closed 7 years ago

crash in npjp2.dll@0x796b with Java SE 7 Update 5

Categories

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

x86
Windows XP
defect
Not set
critical

Tracking

(Not tracked)

RESOLVED INCOMPLETE

People

(Reporter: virgil.dicu, Unassigned)

Details

(Keywords: crash)

Crash Data

This bug was filed from the Socorro interface and is 
report bp-92654b36-b15e-4b87-abd3-d3a042120625 .
============================================================= 
Hit this today on F14 beta9.

Just clicked back from a Java applet on Windows XP. (had a system upgrade running in the backround)

Couldn't reproduce afterwards. Need to also try loading sites from comments-maybe I'll be lucky.

General information: specific to Windows XP, most crashes seem to occur in F13.0.1 (over 300), but present since F 5.0.
95% of crashes happen on Windows XP.

It's #120 top browser crasher on 13.0.1 and #194 in 14.0b8.
Component: General → Plug-ins
OS: Windows NT → Windows XP
Product: Firefox → Core
QA Contact: general → plugins
Summary: crash in npjp2 → crash in npjp2.dll@0x796b with Java SE 7 Update 5
Version: 14 Branch → 13 Branch
Virgil can you please expand on your steps to reproduce here?
(In reply to Anthony Hughes, Mozilla QA (irc: ashughes) from comment #2)
> Virgil can you please expand on your steps to reproduce here?

Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1

Could not reproduce the crash. Tried by following the comment from the Description and the comments from the Socorro reports.
I stumbled upon a similar issue when trying to reproduce this bug, Firefox crashed on me but with a different signature. Filed Bug 768375.

Used the same version of Java SE 7 Update 5. 
I followed the STR:
1. Navigate to a site that tests the java applet:
http://www.w3.org/People/mimasa/test/object/java/
2. Select any of the tests and click very fast on the Back/Forward buttons several times (until Firefox crashes).

Initial crash (Comment 0) occurred after simply clicking Back button while Java was still loading an applet (http://www.w3.org/People/mimasa/test/object/java/) with only one tab opened in the browser and a Service Pack updating in the background.
Add another XP crash to the report. Oracle updated Java 7 to Update 5 this morning and this URL now crashes instantly:
http://www.washingtonpost.com/entertainment/puzzles/daily-crossword
as do the w3.org tests.  I noticed that PC was at FF version 11 so I upgraded to latest (13.0.1) and same thing happens.
It also kills the IE8 installed on this PC.
Mozilla/5.0 (Windows NT 5.1; rv:13.0) Gecko/20100101 Firefox/13.0.1

I could not reproduce the crash on Windows XP with Firefox 13.0.1 and Java SE 7 Update 05. 

Don, could you please post the following:  
-add your crash report from about:crashes (copy -paste the link corresponding to your crash) 
-verify you can reproduce this with a clean profile and post the steps used to reproduce 
http://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles

Thank you.
> Don, could you please post the following:  
> -add your crash report from about:crashes (copy -paste the link
> corresponding to your crash) 
   There is no report in about:crashes -- most recent has a date of 2011. This crashes so fast there isn't time for the Java logo to show up in the applet.


> -verify you can reproduce this with a clean profile and post the steps used
> to reproduce 

    Executed Firefox.exe -p
    Create new profile -- named CleanTest
    Type http://www.washingtonpost.com/entertainment/puzzles/daily-crossword into the address/location bar [Enter]
    Page begins to load and Firefox closes.
    Restarted (to look at about:crashes) and FF attempted to reload the last page and it crashed again.
    Restarted one more time and the message about not being able to restore the previous session popped up.


In the For What It's Worth department... The same thing happens now with IE8.

FWIW - II, This happened immediately after the upgrade.  Also, this upgrade required a reboot which is rare.

FWIW - III the Nereus service (theSkyNet.org) now refuses to start.  This looks like Oracle effed up. I'm going to see if I can find a copy of the Update 4 installer and go back.
I was able to find a JRE7U4 installer so I uninstalled Update 5, verified that the jre7 folder was gone, then installed Update 4 and immediately turned off automagical updates.  The issue went away completely.  Everything that was broken with U5 is now back to normal.  I don't think Oracle's regression tests are covering enough ground.
Component: Plug-ins → Java (Oracle)
Product: Core → Plugins
Version: 13 Branch → 7.x
I was discussing this in another context and one of the people there said:

"Java 7 uses the IPv6 network stack by default (Java 6 uses IPv4). Great, except Oracle have a number of bugs in their IPv6 and lots of VPN software can't handle IPv6 anyway. So "suddenly" Java apps/applets stop working. 

The fix is to include the extra command line switch to the JVM:

-Djava.net.preferIPv4Stack=true

This can be done via the Java plugin control panel on Windows, and for the installed clients (Windows services) I'll be building fixes for this issue soon. The quick fix now is to add this property to the "java.parameters" properties in the Wrapper.conf file (just a text file) in the main skynet installation directory."

I don't know if that explains a total crash of Firefox, and it may be entirely off the mark, but I decided to pass it on anyway. I'm not about to upgrade Java on my WinXP system anyway.
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: 7 years ago
Resolution: --- → INCOMPLETE
Product: Plugins → Plugins Graveyard
You need to log in before you can comment on or make changes to this bug.