1039022 - plugin-container keeps crashing

Status: RESOLVED INVALID

(Core Graveyard :: Plug-ins, defect)

Description

[Steve Chessin]

Attachment: crash.details.txt - the details of the crash from the pop-up.

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:30.0) Gecko/20100101 Firefox/30.0 (Beta/Release)
Build ID: 20140605174243

Steps to reproduce:

In one particular case, I just upgraded to Java 7 Update 65 (from Java 7 Update 60) and when I attempted to run the "Verify Java" applet one gets from
http://www.java.com/en/download/installed.jsp the plugin-container crashed. But I got many of these crashes before I upgraded. I then uninstalled Update 65 and went back to Update 60 and the same thing happened. Note that this all started to happen after I upgraded to Firefox 30.0. (I'm going to go back to Firefox 29.0.1 and see what happens.)


Actual results:

It reports an error, says "click here for details", and after clicking I get the spinning beach ball and then a pop-up that says "Firefox Plugin Process (Java Applet Plug-in) quit unexpectedly".


Expected results:

The Java applet should have run.

Comment 1

[Steve Chessin]

Attachment: Screen shot showing the message that the Java Applet has crashed.

Screen shot showing the message that the Java Applet has crashed. Note that the plugin-container itself did not crash. This is with Java7U60 and both Firefox 29.0.1 and Firefox 28.0.

Comment 2

[Steve Chessin]

I tried the test with Firefox 29.0.1 and Firefox 28.0 with Java 7U60, and each time I got an error message that the applet had crashed (see attachment), but the plugin-container itself did not crash. Will double-check that with Firefox 30.0 the plugin-container itself crashes, and will then redo the tests with Java7U65.

Comment 3

[Steve Chessin]

With Firefox 30.0 and Java 7U60 I get *both* the message that the applet has crashed *and* the pop-up from Problem Reporter that the plugin-container has crashed. Now to try Java 7U65 with Firefox 28.0 and 29.0.1.

Comment 4

[Steve Chessin]

Each version of Firefox (28.0, 29.0.1, 30.0) behaves the same with Java7U65 as it does with Java7U60; that is, the applet is reported as crashing, but in addition in Firefox 30.0 (but not the others) the plugin-container also crashes.

Comment 5

[Steve Chessin]

Attachment: Details display from Problem Reporter

Comment 6

[Steve Chessin]

I don't know if this has anything to do with Java, but ever since I upgraded to Firefox 32.0.1 I get a lot of plugin-container crashes when going to random websites. Apple's Problem Reporter comes up and I send the crash reports to them but I don't know if that gets to you or not, so I'm attaching the details from the latest one. See https://bugzilla.mozilla.org/attachment.cgi?id=8490475 ("Details display from Problem Reporter".)

Comment 7

[Steve Chessin]

I upgraded this week to 33.0.3 and it still happens. I'll attach the latest from Problem Reporter.

Comment 8

[Steve Chessin]

Attachment: Display from Problem Reporter for 33.0.3

Comment 9

[dvandusen]

Attachment: Screen Shot 2016-08-10 at 2.57.18 AM.pdf

Error Display

Comment 10

[dvandusen]

Attachment: plugin-container1.txt

crash report 1

Comment 11

[dvandusen]

Attachment: plugin-container2.txt

crash report 2

Comment 12

[dvandusen]

this bug has been occurring on v47 and v48 of Firefox Mac on one machine. (Another mac machine - recently wiped and rebuilt - works fine).  The crash report is consistent with prior reports. The issue occurs on only one page - the USPTO page - which is hugely troubling, but it may easily be that I only access one page requiring java via firefox.

Comment 13

[Mikhail T.]

I'm seeing such crashes without Java, but whenever the user attempts to view an online video with Firefox-47.0.1 (and some of the earlier versions) -- but only on FreeBSD/i386 (32-bit). FreeBSD/amd64 has no problem. Worse, although meant to insulate the main Firefox from any crashes in plugins, the crashing plugin-container takes the browser down with it at the same time:

pid 1005 (firefox), uid 2000: exited on signal 11
pid 1092 (plugin-container), uid 2000: exited on signal 11 (core dumped)
pid 1278 (firefox), uid 2000: exited on signal 11
pid 1280 (plugin-container), uid 2000: exited on signal 11 (core dumped)
pid 1286 (firefox), uid 2000: exited on signal 11
pid 1288 (plugin-container), uid 2000: exited on signal 11 (core dumped)
pid 1880 (firefox), uid 2000: exited on signal 11
pid 1882 (plugin-container), uid 2000: exited on signal 11 (core dumped)
pid 2167 (firefox), uid 2000: exited on signal 11
pid 2170 (plugin-container), uid 2000: exited on signal 11 (core dumped)

The dumped cores are useless because the executable is stripped -- and was compiling without debugging anyway.

Recompiling plugin-container _without optimization_ seems to work-around the bug, whatever it is. I deliberately replaced just the plugin-container executable with one from a non-optimized build and the crashes stopped -- even though the rest of the firefox binaries were not changed.

Comment 14

[Wayne Mery (:wsmwk)]

Is this even still possible in today's versions?