Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Lolu chungechunge lwabekwa kunqolobane. Uyacelwa ubuze umbuzo omusha uma udinga usizo.

Plugin Java crashes frequently when using multiple tabs, recent development.

  • 6 uphendule
  • 5 zinale nkinga
  • 103 views
  • Igcine ukuphendulwa ngu bagport

more options

When I run a website that requires java in two tabs, then refresh the page back and forth between the tabs, the java plugin crashes every other refresh in one of the tabs. It only happens if i cycle and refresh between the tabs.

This has never been a problem before and started happening this week. It seems related to Firefox updating.

These are my last 5 crash reports:

https://crash-stats.mozilla.com/report/index/bp-f3af567d-3780-43e6-81a6-60b122151113 2015-11-13 09:25 https://crash-stats.mozilla.com/report/index/bp-4394645f-34c7-4e70-aa04-a3c1f2151113 2015-11-13 09:25 https://crash-stats.mozilla.com/report/index/bp-4e4a1fe3-0864-444b-af2a-efc0d2151113 2015-11-13 09:25 https://crash-stats.mozilla.com/report/index/bp-5991017c-3303-449a-95d2-804bb2151113 2015-11-13 09:25 https://crash-stats.mozilla.com/report/index/bp-57c0ac00-5062-4d7c-aab3-d59582151113 2015-11-13 09:25

All Replies (6)

more options

I also tried using two instances of Firefox instead of two tabs and the result is the same. The crashing happens every couple of refreshes in the opposite window or tab.

This issue is now spreading through our offices as updates are rolled out.

I have not updated one client to the latest Java but it still happens. I have updated one client to the latest Java and it still happens.

Refreshing the page where the error message banner appears, removed the error message again.

Okulungisiwe ngu bagport

more options

Are these reports from only one computer?

Product Firefox Version 42.0

Release Channel release OS Windows NT OS Version 6.1.7601 Service Pack 1 ++++++++++++++++++++++++++++++++++++ bp-f3af567d-3780-43e6-81a6-60b122151113 Signature mozilla::plugins

Process Type plugin Java(TM) Platform SE 8 U51 Version

Kernel32.dll = Microsoft

ntdll.dll = Microsoft

java.dll = JavaTM 2 Platform

npjp2.dll = Java(TM) Plug-in

jp2native.dll = Java Platform

jvm.dll = Java HotSpot(TM) = Java(TM) 2 Platform Standard


This is for Sumo's Related Bugs 1222229 RESOLVED DUPLICATE crash in mozilla::plugins::AssertPluginThread ++++++++++++++++++++++++++++++++++++++++++++++++++ Copy of Bug 1222036 - Firefox 42 causes Java to crash - when applet requests permission

"This is a Java bug and an expected crash. See bug 1140616, where we enforce stricter threading checks on plugins which exposed a Java threading bug which could be a security issue."

"The Java plugin will continue to crash like this until Oracle releases a fix."


Perform a System File Check to fix corrupted system files Win 7, 8, 10, Vista: https://support.microsoft.com/en-us/kb/929833

See if there are updates for your graphics drivers https://support.mozilla.org/kb/upgrade-graphics-drivers-use-hardware-acceleration


Make sure your Java (Not JavaScript) is up to date Verify Java and Find Out-of-Date Versions {web link}

Version 8 Update 65 Release date October 20, 2015 http://java.com/en/download/manual.jsp

more options
more options

Correct. Given the extreme simplicity of reproducing the issue I gather that the reports are merely a principle, as they can be pulled from any client at any time if one wish to investigate further.

Java will even crash if the page https://www.java.com/sv/download/installed.jsp is used in multiple tabs while moving back and forth in the java test process.

more options

Try the link with only one tab open. If there is still an issue, use the Java Help Center link.

more options

It works fine using only one tab or one instance of the browser. Our operations can't cope with just one tab, they need multiple tabs up. I understand this problem will not go away until Oracle publish a fix their end.

I take it our current options are to roll back to an older version of Firefox and disabling auto update on all clients, or to use another browser. Consider the amount of work involved.

We have no option but to use another browser. When issues like this arise new versions should not be published until the issue is ironed out both ends. Auto updating into malfunction hardly seems proffessional. No offense to anyone but we have work to do right, we are depending on a browser that works regardless of who's fault it is.