To investigate further, we would need additional details.
Which operating system , browser and browser version are you trying to view this Flash content on?
Chrome 58.0.3029.110 (64-bit),
Edge Microsoft, (38.14393.1066.0),
Firefox 53.0.2 (32 bit)
Chrome 58.0.3029.110 (64-bit),
Edge Microsoft, (38.14393.1066.0),
Firefox 53.0.2 (32 bit)
Mac OS Sierra 10.12.4
Please do help!
We are investigating the issue at our end.
I am facing same problem
i am using windows 10
Google chrome Version 57.11.2987.98
Chromium Version 58.0.2988.0
It crashes too much some times i get error "flash player failed to load"
and lots of time when i am watching videos on some sites screen goes black and notification came for reload except youtube
Did you find any possible cause to this problem yet?
Any suggestion to our flash developers for solving this problem?
We have modified our flash files in YouVivid website to prevent flash player crash in most case.
Now the problem can hardly be observed in the previous URL I provided.
For you to test, we keep the old version here.
Play the above movie and fp171 crash in a few seconds.
From our test, fp crash when loading no-cached external assets including font.
We reduce the crash probabilities by enabling font files caching.
Still, flash player 171 crash often when doing video editing in our website with Mac Safari Browser.
In proxy scanning tools we have seen flash trying to load the same image dozens of times (>30) in the very same moment. All calls returned 200 OK after less than 400 ms
Will Adobe please address this issue. There is clearly a problem. Mac OS Sierra 10.12.3 (16D32) Chrome
Version 58.0.3029.96 (64-bit). Same on Safari and Firefox. This is what I am seeing on adobe sites.
There is a bug file for this and it is being looked at. I'll include the latest information, reported here, in the bug record.
We add cache control mention as above URL to the dynamic generated font files to reduce repeated loading these external assets by flash movie.
Now only when using Google chrome browser fp171 does not crash that often in our website. Using Firefox, edge, safari with Windows or Mac , fp171 crash easily.
Hi, same problem here.
Our app is develop in AS 2.0 (i know it´s old, but is a lot of code to migrate).
Flash crashes on Internet Explorer 11 and with the COM Component (added on a windows forms application), it's random, sometimes crash before 1 minute when i click any button, then with the same button, no crash, but with other action on any time it's crash. Work fine on Chrome and Firefox.
I test with Flash Player Debugger Standalone 18.104.22.168 to see the flashlog.log, and no see any message or warning before it's crash, it's totally random, In fact, sometime crash with no user interaction.
When someone mentions that a image it's calling a lot of times, make me think, because in most cases (not in all, wherefore it's random) crash when show some png files.
Does anybody know if Adobe are doing anything about this? Many sites are now showing the the Flash player has crashed.
As Flash developers we desperately need some guidance if we are to get our sites back up. It's already been a 6 days and not a word from Adobe. What is causing the problem and what can we developers do about it? Although some in this forum have made useful suggestions, none appear to be able to explicitly help us.
We have a file in our system that has done it's job for over 10 years and now it crashes with 22.214.171.124. It does import images dynamically. It does bypass caching as it is an editor and images are often changed during the edit process, so our .swf imports the images from the server each time it runs.
Please Adobe -- HELP
to reproduce the issue , put mouse courser over the swf object without moving or touching your keyboard for 1-2 minutes
then go to an object that perform picture get request you will notice the crash
please take a look at this picture
also visit this game with latest flash 126.96.36.199 and watch any table for 5-10 min it will crash same as all other swf games at facebook
this is very serious issue we are going to move to HTML5 all users are complaining
"Does anybody know if Adobe are doing anything about this?"
Please see my comment #9 - the issue has been reproduced internally and is being worked on. I don't have further information at this time.
this is a proof of the crash of the latest version and how its happen at all browsers with latest 188.8.131.52
i think this bug can be exploited to make more bad damage
see 1 min video if u need the code i will share it
Our system is used by many users.
As time goes on, many inconveniences have arisen and inquiries have increased
Please validate it as soon as possible, please release the modified version.
When will it be fixed?
I want information such as prospects.
Today's beta, 184.108.40.206, includes a fix for this crash. Please go to Download Adobe Flash Player 26 Beta for Desktops - Adobe Labs to download the beta version. Please note the following:
- Flash Player ActiveX beta cannot be installed on Windows 8 and above (due to Microsoft embedding Flash Player ActiveX Control in IE and Edge)
- The stable version of Flash Player needs to be uninstalled prior to installing the beta version. Uninstaller is posted at Uninstall Flash Player for Windows
- The beta version of Flash Player needs to be uninstalled prior to reverting to the stable version. Use the beta uninstaller posted at the bottom of the Download Adobe Flash Player 26 Beta for Desktops - Adobe Labs page to uninstall the beta version before installing the stable version.
Please post back here if the beta build fixes the crash for you. If not, please provide specific details on what is happening, and include the OS and browser version.
We are also experiencing this very impactful issue. The 26 Beta seems to resolve the issue, but it's not feasible to have everyone take advantage of this workaround. Any idea if this fix will be patched on 25? Or any eta on the 26 release?
Also any chance you can share a link to the bug for this in tracker.adobe.com?
At this time, I'm not aware of a planned out-of-band release for this issue. Flash Player's normal release cadence is the second Tuesday of the month (patch Tuesday) with version 26 scheduled to be released the second Tuesday in June.
Tracker link: https://tracker.adobe.com/#/view/FP-4198402
Thanks for the update Maria. I'm wondering if you can provide any insight as to what exactly causes the crash so that we might possibly make changes code side to mitigate crashes.
Our application loads and shows external photos and from various tickets opened around this issue some are reporting that this might be to blame. Any insight would be appreciated, as I'd hope to find a work around to buy time until the next release.
I am glad to see that there is a fix in the works but to have to wait an entire month for the next whole number version update... well I'm not sure my business can survive another four weeks of frustrated customers who can't get their work done.
This is a MAJOR issue for those of us who depend on Flash for our daily bread... my seventeen year old company and software application I built on Flash back in 2000 could literally die before mid-June. Is there ANY way we could get a patch for 25? Or am I going to have to tell my customers to suck it up and double down on our initiatives to abandon this platform entirely?
I totally agree with Alex, we are in exactly the same position. Our business is Flash based and now it is simply out of order. The fact that Adobe can let us wait this long for a fix is pretty outrageous, it is absolutely gutting news that we will have to watch our business dwindle for nearly another whole month. 'Patch Tuesday' is in fact June 13th 2017.
I am sure everyone here would welcome some better news soon. All have invested money, time and passion with Flash over nearly two decades. We really deserve something better that this.
Again I say; Please Adobe don't do this to us. Patch it so people who auto -updated to 220.127.116.11 can receive an incremental update with a fix.
Chris. Rather than everybody change their code, would not be easier to just release the new player before June 13? Even if JS323P has the answer, what would be the point in us spending many hours to correct our code for a broken plugin and then change it all back three and a half weeks later. What a colossal waste of energy!
We didn't really find a solution. What we have done only reduce the crash frequency for Google Chrome browser with flash player 18.104.22.168. Beside Chrome, fp171 still crash easily with Firefox, Edge, and Safari.
For your reference, we have many dynamic generated swf files including fonts data that should be pre-loaded into main flash movie before playing. And we found these font files caching didn't really work since we didn't implement cache control in server script which generate the font files. Flash movie crash often when loading external files on playing movie. So we add the cache control in the font file generator script to enable loading font files from cache rather than loading from server again. The following Stack Overflow answer is what we implement.
Same as other affected flash websites , we are expecting for flash player 26 to be released ASAP.
I can confirm that the bug (at least to some measure) has to do with loading of external images. Enabling some sort of caching for those images definitely improves things (far less crashing). But this is a temporary measure and understandably not practical for most folks.
I would certainly upvote an out-of-band patch for this. If not for the significant impact to those with affected products, but at a minimum for the even more number of people using those products and who will attribute the incessant crashing to "Flash in general" and provide more impetus to disabling the technology in general.
I know this is not critical security vulnerability territory (where Adobe would presumably be more inclined to patch out of band), but I wouldn't underestimate the impact of this bug.
Dear Maria. Via email this morning I read the post from Lizzie Borden8 who is obviously very angry. Have you decided to moderate this message out? I am now wondering how many more messages expressing deep anger at Adobe's arrogance have been culled from this forum.
Well what she said is what we all feel and have thus far been too polite to say. May I ask then Maria, why are Adobe being so stubborn? What is the reason for it? Have you escalated this to higher authorities? Do they realise they are putting Adobe customers' livelihoods at risk? Are Adobe retiring Flash? Is this the end? Why are you treating the Flash player like legacy software? After so many years of development, despite the screaming anti flash movement, this is how the faithful are treated.
I'm with you Lizzie, angry, frustrated, helpless. Adobe don't listen, Adobe don't care. Our voices are nothing but a mosquito bite to them. Adobe are happy to take our money but feel no obligation to actually fix broken software. Shame on you Adobe. Shame, shame, shame.
We encountered a similar, but different, issue that cause FP 25 crash.
In our case it happens when uploading a file to our flash-based application.
The upload adds an item on a list, alongside triggering some background updates and rendering.
The upload goes well, but once the item is added Flash Player crashes.
This happens in IE11 & Firefox on Windows 7, also with FP 26 Beta (debugger version at least on Firefox).
Crashes in similar scenario started happening often also in Chrome.
Please advise ASAP
Thanks in advance,
I'm actually shocked someone was able to read my post before they deleted it & yes THEY deleted it, I guess they didn't like me telling the truth & I stand by what I said in my post that was deleted, this should be fixed NOW, not whenever they feel like it (ie: mid June!)
Dear Maria. Via email this morning I read the post from Lizzie Borden8 who is obviously very angry. Have you decided to moderate this message out?
No, I did NOT moderate/report this user. I participate on the forums, Mon-Fri during normal business hours in-between my normal workload. I receive email notifications for ALL posts and did see that post. There are many ways to get a point across without being abusive or cursing. Abusive content can be reported for deletion . With the information provided it's difficult at best to determine if the crashes they are experiencing are related to this issue for this topic.
As for escalating this - management is aware of the crash. I do not have any information as to whether an out-of-band release will be done to address this.
Have you seen my previous reply in this thread?
Should the next version fix all recent crashes?
From searching through Google I see recent complaints on Facebook (flash-based) video player crashes, online-games crashes etc.
At least over here installing the beta version (26) didn't solve the issue.
Please review all the recent changes implemented in Flash Player 25 and check what could have caused this increase in crashes.
Thanks in advance,
Yes, the next version of Flash will have a fix for the bug originally reported in this thread. We released another beta today that resolves a few other problems (including an issue with removeMovieClip()). Evyatar, if you have an issue that is still not solved, please reach out to me (firstname.lastname@example.org) with a new bug number from tracker.adobe.com that walks us through the exact reproduction steps. We'll investigate immediately.
I know that many of the developers on this thread would like to see an immediate release of the player that addresses this bug. We take this very seriously and apologize that we didn't catch this issue before our release. We understand the severity, and we immediately started an investigation into the issue when first raised. As noted earlier in this thread, we put out a beta that we believe addresses the problem just a week after the initial report.
As part of that investigation, we reached out to all of the major browser vendors to get a better understanding of the crash volume that this bug has caused. The browsers, not Adobe, receive the crash reports sent in by customers. Based on their feedback, we've determined that the number of systems and content impacted has not risen to a level where an immediate update is required. I know this is disappointing to hear, but please keep in mind that every time an update occurs, over a billion systems are touched. This takes coordination not just from Adobe, but Google & Microsoft (who ship the player with their platforms), system admins across the globe, and much more.
Our recommendation at this time is to point impacted customers to our current beta or hang tight until our next release, currently scheduled for June 13th. If you believe our current beta does not resolve the problem, please contact us immediately through tracker.adobe.com and this thread with detailed reproduction steps.