Plenty of other questions providing less information have been answered on this forum without getting that blunt response.
As I said, I am running Windows 8.1: it's 64 bit with all updates applied. The latest version of Firefox is 33.1 (20141106). Your version of Flash that I'm having trouble with is 220.127.116.11.
As an example, at Adobe Flash Player | Overview I get the effect below after the app has sat doing nothing for a while.
On some other sites after a while I get a box with 2 buttons offering to end the app or to continue with it, but nothing useful happens.
Thanks for the details. We tend to get waves of similar questions, so I can usually guess based on really sparse information, but I didn't have a reasonable theory based on the information you provided.
I don't have a lot of suggestions at this point. Do you experience similar performance issues when using Internet Explorer or Google Chrome?
It seems to work OK on Explorer.
It's important to point out that both Adobe and Microsoft made a tremendous effort in tuning the Internet Explorer experience for Windows 8 and higher. The latest versions of IE offer a fast, modern plug-in architecture that efficiently offers defense-in-depth protection against the modern generation of security threats (as opposed to the sandboxing approach that we retrofit to Firefox). Similarly, Google Chrome provides a modern, secure plug-in architecture and invests heavily in making the Flash experience in the browser great. I'm a Firefox fan as well, but the reality is that you might be more satisfied with your experience when using a different browser.
For the crash, I'd be happy to take a look at the crash analysis to see if I can find anything useful.
In Firefox, if you type about:crashes in the address bar, you should get a list of recent crashes.
Click each link to submit it to the Mozilla crash reporting system.
Copy the address from the resulting window into a reply here.
Many thanks. Here are some recent ones:
All of these are related to IPC (Inter-Process Communication) between Firefox and Flash. There is a generic class of hangs that occurs when messages between Flash and Firefox are delivered out of order, or messages between them are dropped. One side of the call sits around waiting for a response until they hit the 30-second timeout, at which point Firefox concludes that the conversation is hung and (safely) kills the Flash Player process.
We've spent a lot of time looking into this, but there is no magic bullet. At a high level, it seems like there's simply too much IPC communication happening due to the multiple, redundant layers of brokering happening in the Firefox plug-in architecture. In order to bring modern security defenses to the table on Firefox, we had to retrofit a sandboxing approach, and then Firefox adds two additional layers of abstraction above us. This means that every message gets passed around four times. Experimentation indicates that disabling some of those layers of communication decreases the traffic and the problems go away; however, by disabling sandboxing in Flash, you leave yourself at a significantly higher risk for a malware infection, and by disabling the layers in Firefox, your other plug-ins can crash the browser.
Long story short, you're better off using another browser, like Google Chrome or Internet Explorer, both of which have invested heavily in modernizing their plugin architectures over the last few years. While we would welcome a modernized plugin architecture in Firefox that was capable of delivering both the security and performance required for modern content and the current threat landscape, Mozilla envisions a world without plug-ins, and does not see investment there as a priority.
OK, many thanks for that. Looks like I'll be giving Chrome a look.