1122646 - Any Flash elements on a page refuse to run.

Status: RESOLVED INCOMPLETE

(Core Graveyard :: Plug-ins, defect)

Description

[benrobart]

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

Steps to reproduce:

I opened a page with Flash on it.


Actual results:

My browser locked up for a few minutes then I get an error of "The instruction at 0x00000000 referenced memory at 0x00000000. The memory could not be written" (The 0x00000000 changes to something new each time).

This happens on Facebook, IGN, and Imgur in particular. It works the first time I open Firefox after I reinstall Flash, then when I re-open Firefox it happens again.

This isn't an issue with Flash as it works fine in Internet Explorer.

The bug still occurs in Firefox's safe mode.


Expected results:

Flash should work?

Comment 1

[:Gijs (he/him)]

(In reply to benrobart from comment #0)
> User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101
> Firefox/35.0
> Build ID: 20150108202552
> 
> Steps to reproduce:
> 
> I opened a page with Flash on it.
> 
> 
> Actual results:
> 
> My browser locked up for a few minutes then I get an error of "The
> instruction at 0x00000000 referenced memory at 0x00000000. The memory could
> not be written" (The 0x00000000 changes to something new each time).

I'm assuming this crashes the browser? Or doesn't it? Just flash, maybe?

> This happens on Facebook, IGN, and Imgur in particular. It works the first
> time I open Firefox after I reinstall Flash, then when I re-open Firefox it
> happens again.

Have you tried reinstalling Firefox instead? You can choose not to delete your bookmarks and settings and so on.

If that doesn't fix it, please try what happens if you create a new profile, even temporarily: https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-profiles .

Comment 2

[benrobart]

(In reply to :Gijs Kruitbosch from comment #1)
> (In reply to benrobart from comment #0)
> > User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:35.0) Gecko/20100101
> > Firefox/35.0
> > Build ID: 20150108202552
> > 
> > Steps to reproduce:
> > 
> > I opened a page with Flash on it.
> > 
> > 
> > Actual results:
> > 
> > My browser locked up for a few minutes then I get an error of "The
> > instruction at 0x00000000 referenced memory at 0x00000000. The memory could
> > not be written" (The 0x00000000 changes to something new each time).
> 
> I'm assuming this crashes the browser? Or doesn't it? Just flash, maybe?
> 
> > This happens on Facebook, IGN, and Imgur in particular. It works the first
> > time I open Firefox after I reinstall Flash, then when I re-open Firefox it
> > happens again.
> 
> Have you tried reinstalling Firefox instead? You can choose not to delete
> your bookmarks and settings and so on.
> 
> If that doesn't fix it, please try what happens if you create a new profile,
> even temporarily:
> https://support.mozilla.org/kb/profile-manager-create-and-remove-firefox-
> profiles .

It crashes Flash but not the browser.

I've reinstalled Firefox, I've even installed Nightly and that doesn't fix it. Creating a new profile doesn't help either.

Comment 3

[:Gijs (he/him)]

Can you check about:crashes - does that list recent crash IDs corresponding with the times when flash crashed, and if so, can you copy/paste some here? If not... hum... can you go to about:support and copy the raw data with the button, and paste it as a text attachment at https://bugzilla.mozilla.org/attachment.cgi?bugid=1122646&action=enter ?

Comment 4

[benrobart]

Attachment: about:support

Hi,

My browser has crashed recently on a frequent basis, though I'm not sure if it's tied in with the Flash crashes - Though I can say without a doubt that Flash often crashes without crashing my entire browser.

Here are some of my recent crashes (Which seem to be linked to Enhanced Steam, so most likely unrelated to Flash):
https://crash-stats.mozilla.com/report/index/5b9d5ae8-3027-42f8-b1dc-192122150117
https://crash-stats.mozilla.com/report/index/d2b7b7c4-2bf6-4ff8-ba19-1fe1e2150117
https://crash-stats.mozilla.com/report/index/26c79363-5500-4279-be5c-e21a82150117
https://crash-stats.mozilla.com/report/index/a8619274-d448-4b86-b017-b4f172150116

I've attached the about:support page to this comment.

Thanks for your help in fixing this.

Comment 5

[benrobart]

Can confirm that my browser no longer crashes after disabling Enhanced Steam - Though I am still encountering the Flash issues, which is of course what this thread is about!

Comment 6

[:Gijs (he/him)]

(In reply to benrobart from comment #5)
> Can confirm that my browser no longer crashes after disabling Enhanced Steam
> - Though I am still encountering the Flash issues, which is of course what
> this thread is about!

Some of these are flash crashes alright ( https://crash-stats.mozilla.com/report/index/d2b7b7c4-2bf6-4ff8-ba19-1fe1e2150117 , https://crash-stats.mozilla.com/report/index/a8619274-d448-4b86-b017-b4f172150116 ). I just wish I could tell you much more than that - we've seen that signature for lots of things, but always have trouble reproducing - and the crash in flash itself isn't something we ourselves can fix...

I'm moving this to the right place... maybe bsmedberg has ideas about further steps to troubleshoot this? If you're able to reproduce this so easily, maybe it's possible to narrow down the cause of the issue further. Benjamin?

(meanwhile, I chased some other people about the Steam issue in bug 1117873 - thanks for mentioning that!)

Comment 7

[benrobart]

Thought I should update you on this - I took a look at the flash crashes you linked to, and look at pages linked from there to people with the same issue.

Sure enough, disabling "protected mode" in Flash seems to have worked for now - Not a solution by far, but a workaround that I'm happy enough with for now.

Any permanent fix would be appreciated, though!

Comment 8

[Benjamin Smedberg]

Kamil, can you try and reproduce this? If we have reliable STR with enhanced steam and protected mode on, there are a couple things we should do from an engineering perspective:

1) figure out why you're seeing a windows crash dialog and this isn't being caught by the Firefox crash reporter
2) From the symptoms it sounds like a plugin hang that is being reported as a crash, so we'd be undercounting hangs. We should figure that part out.
3) Perhaps spend some time diagnosing the problem itself.

Comment 9

[Kamil Jozwiak [:kjozwiak]]

So I tried reproducing this several times using the same build (20150108202552) on several machines without any luck. I made sure that protected mode was enabled and loaded several websites that used flash including the ones listed in comment # 0 (Facebook, IGN, and Imgur)

I did run into a Steam Enhanced crash on m-c when e10s was enabled so I've added a comment in bug # 1117873 comment # 21.

* fx build id: 20150108202552 [changeset: 32e36869f84a]
* flash -> Version: 16.0.0.296
* Enhanced Steam	 7.2.3

OS's used:

* Windows 7 x64
* Windows 7 x86
* Windows 8.1 x64

I took a look at a friends machine who uses fx and visits IGN on a regular basis, he has protected mode turned on and hasn't noticed any crashes while using IGN. However he said that flash crashes often when visiting ESPN FC and sites that stream music. I got a few flash crashes within minutes after opening a few video tabs via ESPN FC but didn't reproduce anything that's similar to comment #0:

* https://crash-stats.mozilla.com/report/index/9a1e8811-a77a-4705-9cc4-5d0212150129

Benjamin, is there anything that perhaps I've missed that I could run to see if I can reproduce the problem?

Benrobart, can you still reproduce this when re-enabling protected mode? Could you check about:plugins and let me know what version of flash you're currently using? (I'm assuming it's most likely the latest)

Comment 10

[benrobart]

(In reply to Kamil Jozwiak [:kjozwiak] from comment #9)
> So I tried reproducing this several times using the same build
> (20150108202552) on several machines without any luck. I made sure that
> protected mode was enabled and loaded several websites that used flash
> including the ones listed in comment # 0 (Facebook, IGN, and Imgur)
> 
> I did run into a Steam Enhanced crash on m-c when e10s was enabled so I've
> added a comment in bug # 1117873 comment # 21.
> 
> * fx build id: 20150108202552 [changeset: 32e36869f84a]
> * flash -> Version: 16.0.0.296
> * Enhanced Steam	 7.2.3
> 
> OS's used:
> 
> * Windows 7 x64
> * Windows 7 x86
> * Windows 8.1 x64
> 
> I took a look at a friends machine who uses fx and visits IGN on a regular
> basis, he has protected mode turned on and hasn't noticed any crashes while
> using IGN. However he said that flash crashes often when visiting ESPN FC
> and sites that stream music. I got a few flash crashes within minutes after
> opening a few video tabs via ESPN FC but didn't reproduce anything that's
> similar to comment #0:
> 
> *
> https://crash-stats.mozilla.com/report/index/9a1e8811-a77a-4705-9cc4-
> 5d0212150129
> 
> Benjamin, is there anything that perhaps I've missed that I could run to see
> if I can reproduce the problem?
> 
> Benrobart, can you still reproduce this when re-enabling protected mode?
> Could you check about:plugins and let me know what version of flash you're
> currently using? (I'm assuming it's most likely the latest)

I'm running the latest version of Flash from Adobe's website. Re-enabling protected mode causes the problem to arise again, unfortunately. I'm not sure what the effect of disabling protected mode is (I assume it's just a security thing that doesn't have too much of an effect), but I'm happy to use this as a workaround until this is fixed!

Comment 11

[Kamil Jozwiak [:kjozwiak]]

Attachment: beforeCrash.png

Thanks for the info benrobart, much appreciated.

Benjamin, I think I reproduced a similar issue on my Nightly build. I had the plugin-container.exe crash on me several times over the weekend with a windows crash rather than a Firefox Crash. I only received the Mozilla Crash Reporter once but when I attempted to send the report, everything hung and it never uploaded the report. I let the crash reporter run for about 2 hours but it never completed.

I added some screenshots to illustrate the state of fx and the crashes that I go:

* beforeCrash.png - before the crash.. all the flash components on the page started appearing black and fx became almost unusable.. as soon as I resized the the browse, it crashed. (I'm guessing it crashed during the reflow of the page when re-sized)

* firstCrash.png - this is the first crash that I received. This was the only time that I got the fx crash reporter but it never ended up sending the report as mentioned above.

* secondCrash.png & thirdCrash.png - same crashes and used the same STR

STR: (not, this takes a LONG time to reproduce but I got the crash 3 different times using this method)

* download the latest nightly
* opened the following websites
** www.premierleague.com/en-gb.html
** https://www.youtube.com/watch?v=K7SYvgB6SZ4 (pressed play and paused about 2-3 minutes into the clip)
** http://www1.skysports.com/watch/video/sports/football/9683332/the-art-of-scouting-episode-1 (let it play and paused it)

Once I had those websites opened, I left "www.premierleague.com/en-gb.html" as the default tab and let the transitions on the website running over and over. It basically changes the the front page every few seconds. If you leave this running long enough, the RAM of fx starts increasing slowly including the plugin-plugin container. Once you leave it going for 2-3 hours everything will start appearing as black squares and you'll get something along the lines of "beforeCrash.png". Once that happens, your bound to crash. Ad this point, fx was using around 1.5GB 2GB worth of memory.

Comment 12

[Kamil Jozwiak [:kjozwiak]]

Attachment: firstCrash.png

Comment 13

[Kamil Jozwiak [:kjozwiak]]

Attachment: secondCrash.png

Comment 14

[Kamil Jozwiak [:kjozwiak]]

Attachment: thirdCrash.png

Comment 15

[benrobart]

(In reply to Kamil Jozwiak [:kjozwiak] from comment #11)
> Created attachment 8557672 [details]
> beforeCrash.png
> 
> Thanks for the info benrobart, much appreciated.
> 
> Benjamin, I think I reproduced a similar issue on my Nightly build. I had
> the plugin-container.exe crash on me several times over the weekend with a
> windows crash rather than a Firefox Crash. I only received the Mozilla Crash
> Reporter once but when I attempted to send the report, everything hung and
> it never uploaded the report. I let the crash reporter run for about 2 hours
> but it never completed.
> 
> I added some screenshots to illustrate the state of fx and the crashes that
> I go:
> 
> * beforeCrash.png - before the crash.. all the flash components on the page
> started appearing black and fx became almost unusable.. as soon as I resized
> the the browse, it crashed. (I'm guessing it crashed during the reflow of
> the page when re-sized)
> 
> * firstCrash.png - this is the first crash that I received. This was the
> only time that I got the fx crash reporter but it never ended up sending the
> report as mentioned above.
> 
> * secondCrash.png & thirdCrash.png - same crashes and used the same STR
> 
> STR: (not, this takes a LONG time to reproduce but I got the crash 3
> different times using this method)
> 
> * download the latest nightly
> * opened the following websites
> ** www.premierleague.com/en-gb.html
> ** https://www.youtube.com/watch?v=K7SYvgB6SZ4 (pressed play and paused
> about 2-3 minutes into the clip)
> **
> http://www1.skysports.com/watch/video/sports/football/9683332/the-art-of-
> scouting-episode-1 (let it play and paused it)
> 
> Once I had those websites opened, I left "www.premierleague.com/en-gb.html"
> as the default tab and let the transitions on the website running over and
> over. It basically changes the the front page every few seconds. If you
> leave this running long enough, the RAM of fx starts increasing slowly
> including the plugin-plugin container. Once you leave it going for 2-3 hours
> everything will start appearing as black squares and you'll get something
> along the lines of "beforeCrash.png". Once that happens, your bound to
> crash. Ad this point, fx was using around 1.5GB 2GB worth of memory.

Thanks for looking into this - I believe this could be a separate bug as my Flash Player would crash instantly rather than take a few hours to do so, though it could well be the same, couldn't say for certain.

Comment 16

[Benjamin Smedberg]

Yes, Kamil's issue is different. A memory issue, perhaps worth filing, but unrelated to the first report here.

Comment 17

[Kamil Jozwiak [:kjozwiak]]

Thanks Benjamin, created Bug # 1128999. I'll keep my eye out for this but so far it appears to be very elusive!

Comment 18

[Wayne Mery (:wsmwk)]

Are you still seeing this crash?