1098043 - Content using Flash Player does not load

Status: RESOLVED WORKSFORME

(Firefox :: Untriaged, defect)

Description

[Jeromie Clark]

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:36.0) Gecko/20100101 Firefox/36.0
Build ID: 20141112030202

Steps to reproduce:

Using Nightly 36.0a1 (2014-11-12) with Electrolysis enabled

Go here: http://www.homestarrunner.com/


Actual results:

You get a grey box where Flash content should be 


Expected results:

Flash content renders

Disable Electrolysis and Flash works as expected.

Comment 1

[:Gijs (he/him)]

What version of Flash?

Comment 2

[akulle12]

(In reply to :Gijs Kruitbosch from comment #1)
> What version of Flash?
This happens to me too. I am using the latest version, 15.0.0.223

Comment 3

[Matthias Versen [:Matti]]

Works for me with a local trunk build (1h old) and flash 15.0.0.223 on windows7

Comment 4

[akulle12]

It works for me too now, after I updated to the latest Nightly.

Comment 5

[Jeromie Clark]

I'm using the latest Flash Player, 15.0.0.223. I see this issue in the current Nightly as well - (2014-11-13)

Comment 6

[Allison Naaktgeboren :ally]

Hey, could you retest on tomorrow's Nightly? We just landed a lot of plugin work. :)

Comment 7

[Jeromie Clark]

No problem, thanks.  Feel free to reach out if there's anything we can do to help with plug-in testing (you want some targeted feedback on something that might be risky, etc).

Comment 8

[Jim Mathies [:jimm]]

This should be fixed in the latest nightly on Windows and Linux. wfm as well.

Comment 9

[Paul Silaghi, QA [:pauly]]

WFM in 36.0a1 (2014-11-17) e10s ON

Comment 10

[Chris Peterson [:cpeterson]]

Jeromie, can you please verify whether jimm's recent plugin fixes fixed Homestar Runner for you?

Comment 11

[Jeromie Clark]

Hey Chris!  It works in 32-bit Firefox now, but not in 64-bit.

Comment 12

[Jim Mathies [:jimm]]

Not sure what our plans are for 64-bit builds, but I assume a bug is on file/plan is in place. Will try to track that info down.

Comment 13

[Jeromie Clark]

FYI, this is busted again in Firefox Nightly 36.0a1 x86 with E10S enabled.

Comment 14

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

[Tracking Requested - why for this release]:

I can reproduce this in a non-e10s window (as well as an e10s window). This is on Windows 8.

Comment 15

[Chris Peterson [:cpeterson]]

Jim: could this Flash regression be fallout from your plugin process changes? Bill can repro on Windows 8 with and without e10s.

Jeromie: in comment 13, you said Firefox 36 (on the Nightly at that time, now on Aurora) was busted. Was this a regression in Firefox? Were you using the same Flash Player build in comment 13 as earlier?

Comment 16

[Jeromie Clark]

It was fixed, but then regressed within a day or two.  Based on the timeline, I think 36.0a1 (2014-11-17) is the last build where Flash worked with E10S enabled, or at least it's pretty close.  If you need more precision, let me know and I'll track it down.

Comment 17

[Jim Mathies [:jimm]]

wfm, win8, with e10s and non-e10s.

Comment 18

[Jim Mathies [:jimm]]

Lets ask QA to check this. AFAICT we're in good shape. Note, on win8 devices with touch screens, you have to add:

browser.tabs.remote.autostart.disabled-because-using-a11y = false
accessibility.force_disabled = true

to get e10s running.

Comment 19

[Liz Henry (:lizzard) (relman/hg->git project)]

On 37.0a1 (2014-12-22) with e10s enabled there was only a grey box for Flash content on http://homestarrunner.com. Still true for today's Nightly in e10s and non-e10s windows.

Comment 20

[Sylvestre Ledru [:Sylvestre]]

I must admit that I am lost with this bug. I would like to wontfix it for 36 as it seems to have a low impact.

So, two questions:
* Can we reproduce this issue all the time in 36 (without e10s)?
* Does it affect a lot of users?

thanks

Comment 21

[Jeromie Clark]

This content works fine with E10s disabled.  Basically, no content that uses Flash loads when E10S is enabled.

Comment 22

[Sylvestre Ledru [:Sylvestre]]

OK, thanks. Since we don't ship e10s in 36, I am going to untrack it.

Comment 23

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

Liz and I have been able to reproduce this with e10s disabled. So I think we should still track.

Comment 24

[Sylvestre Ledru [:Sylvestre]]

ok but my questions in comment #20 are still relevant :)

Comment 25

[Liz Henry (:lizzard) (relman/hg->git project)]

This works for me on 36 on Mac 10.10 and Win 8.1. I can't reproduce it. Bill, I think we should probably wontfix this unless you can still reproduce it and we know there still is a problem.

Comment 26

[Jeromie Clark]

I'm reproducing this consistently on Win7 x64.

Comment 27

[Jeromie Clark]

(With 32-bit Firefox Nightly)

Comment 28

[Arthur K. (he/him)]

I'm curious if Adobe's had some issues lately with Flash as I've seen them release three updates (.257, .287, .296) in the past 2-3 weeks. Even today, 16.0.0.305 was released. They usually wait to release on Patch Tuesday.

Comment 29

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

I tested this again on Windows 8. First, I found that, embarrassingly, I didn't have Flash installed. We're supposed to show a "Plugin not found" UI. That UI appears to be broken in Nightly, Aurora, and beta. It seems to work in release though.

When I installed Flash, I can reproduce a problem in e10s on nightly. I can't reproduce anything without e10s. So I reset the tracking flags.

The problem I can reproduce with e10s is as follows. The page shows all black when it loads, but only if the cursor is not over the plugin area. If the cursor is moved over the plugin area, then the plugin draws. If I switch tabs, the plugin draws. So somehow we're not invalidating correctly or something.

Comment 30

[Arthur K. (he/him)]

(In reply to Liz Henry :lizzard from comment #25)
> This works for me on 36 on Mac 10.10 and Win 8.1. I can't reproduce it.
> Bill, I think we should probably wontfix this unless you can still reproduce
> it and we know there still is a problem.

Same here. I cannot repro either on 36.0b6 nor on 37 (20150205004014).

Comment 31

[Jim Mathies [:jimm]]

(In reply to Bill McCloskey (:billm) from comment #29)
> The problem I can reproduce with e10s is as follows. The page shows all
> black when it loads, but only if the cursor is not over the plugin area. If
> the cursor is moved over the plugin area, then the plugin draws. If I switch
> tabs, the plugin draws. So somehow we're not invalidating correctly or
> something.

This is a side effect of the compositor work that just landed - bug 1128079.

Comment 32

[Jim Mathies [:jimm]]

bah, sorry, I didn't not intend to close this.

Comment 33

[Trevor Rowbotham [:rowbot]]

:billm, does setting dom.ipc.plugins.sandbox-level.flash to 0 (restart the browser for it to take effect) make the flash content render properly for you?

Comment 34

[Bill McCloskey [inactive unless it's an emergency] (:billm)]

No, it doesn't seem to have any effect.

Comment 35

[Ryan VanderMeulen [:RyanVM]]

This works for me on Win10 on Nightly with e10s enabled and on all recent Fx releases. Jeromie, is this still a problem on your end?

Comment 36

[Ryan VanderMeulen [:RyanVM]]

Closing this as incomplete due to inactivity and lack of response from the reporter. Feel free to reopen the bug if the issue still reproduces on a current build.