369328 - crash on display of http://www.acts.co.za/ect_act/

Status: RESOLVED INCOMPLETE

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

Description

[Jaco Kroon]

User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.1) Gecko/20070111 BonEcho/2.0.0.1
Build Identifier: Mozilla/5.0 (X11; U; Linux x86_64; en-US; rv:1.8.1.1) Gecko/20070111 BonEcho/2.0.0.1

Can't say much more, it crashes ... not sure what is wrong but the link concistently manages to crash firefox so I'm pretty sure it should be reproducible for whomever needs to debug this.  Please let me know if there is anything further I can do to assist. 

Reproducible: Always

Steps to Reproduce:
1.  Start firefox
2.  go to http://www.acts.co.za/ect_act/
3.  watch as firefox just closes...

Comment 1

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1

It does not crash, but the applet doesn't load either. I get the following message instead:
 
The applet did not load properly. Your current Netscape profile needs to be modified. Select "Remember this decision" and click "Grant" when prompted to allow modifications. Click OK to proceed.
Using the latest Java version.

The same happens in the latest Windows trunk build and also in older builds.

Comment 2

[[:Aleksej]]

Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.8.1.2) Gecko/20070220 Firefox/2.0.0.2
Java(TM) Plug-in 1.5.0_10

No crash, but the applet didn't work first, then after some activity (especially switching the tabs with hot keys), the pages become selectable.

Comment 3

[Carsten Book [:Tomcat]]

Jaco, do you still crash with the latest offical Firefox Release 2.0.0.4 ?

Comment 4

[Jaco Kroon]

Don't have 2.0.0.4 yet, but 2.0.0.3 seems to survive, so is it safe to assume that 2.0.0.4 is ok as well?

Doesn't actually seem much more useful since the applet doesn't seem to load, but i'd rather have dysfunctional than crashing.  I suspect this may be a coding error on their side, so if you can confirm then I can contact them and you're welcome to close.  Reducing prioriy anyways.

Comment 5

[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.