![]() As a guide, here's some information that would really help when looking into problems: Read Before Posting: How To Get A Useful Answer To Your Question The closer you can get us to reproducing a problem, by including basic information about your system and affected content, the closer we'll be to fixing it. As a general rule, using a reasonably modern OS (Win7/MacOS 10.9 or higher) and a browser with a modern plug-in architecture (IE on Win8+, Google Chrome everywhere) is generally going to yield more stable results than older architectures like NPAPI where we're trying to balance modern needs with architecture from the '90s.Īgain, generalities don't really help solve the specific crash that you're experiencing, when using your machine, to view the content that you frequent. That said, specificity is key to getting the issue you're experiencing fixed. The problems that it solves are extremely complex, and the challenge of both providing backwards compatibility and supporting 1.2 billion installations and the array of hardware that encompasses is a tremendously difficult task. It's a very heavily controlled and highly scrutinized codebase. ![]() Flash Player is in the neighborhood of 1.5 million lines of C++ code, and we subject it to a battery of tests, including manual and automated source code analysis both by Adobe engineers, outside consultants and engineers from Microsoft, Intel, nVidia, AMD, Google, etc. Unfortunately, intermittent, random problems with nebulous symptoms tend to linger unsolved. If we can reproduce a problem, it's usually very straightforward to fix. If you have steps that consistently reproduce the problem, that's also incredibly helpful. ![]() (There's a long story from the 90's about why they both have Shockwave in the name.)Ĭrashes and hangs have distinct root-causes, and we would need to look at these on a case-by-case basis.įor each crash listed, click the link to submit it, then copy the resulting URL into this thread. The test that you pointed to is for the Shockwave Player, which is different from Flash Player. ![]() Would appreciate some help to get this error permanently resolved. This problem was causing Firefox to crash, but Firefox is now stable- only receiving the flash error messages. I've tried most of the fixes online: disabling hardware acceleration (works for a few hours then the problem comes back), uninstalling then reinstalling adobe flash, shockwave, & silverlight (worked for a few days, now the problem is back), clean install of Firefox, changing flash permissions in Firefox to ask to activate, and all the fixes listed here: Flash Player games, video, or audio don't work | Windows. The server encountered an error while processing this request: On the Adobe test page: Adobe - Test Adobe Shockwave Player I can see the Shockwave Flash test message, but get the following error message when trying to view the Flash Player test: Internal Server Error I keep getting the error messages: "Adobe Flash Player 14.0 r0 has stopped working" and "Unresponsive Plug-in: Shockwave flash may be busy or may have stopped responding." when trying to watch videos from youtube, hulu, netflix, etc. Using other browsers may or may not help, I haven't tested it myself.Hi, am running Flash in Firefox on Windows. But note that most people use Chromium-based browsers, so websites may not be optimized to run their best on other browsers. You could also try using Scratch with different browsers, as Chromium-based browsers like Chrome, Brave Browser, and Microsoft Edge do use a little more resources than other browsers like Firefox. You will also see the memory usage go up when using memory-intensive Scratch projects. If you're concerned about why Scratch project players keep crashing, you could try opening Task Manager by pressing Ctrl+Shift+Esc, clicking “more details” if you haven't already, and there you might find out what's eating up all the memory, causing slowdowns, or other things. I have 16 GB of RAM which means I can run some of the most memory-intensive projects, but 8 GB would probably be enough. Definitely consider using 8 GB of RAM or more if you continue to have project player crashes. If you run low on RAM while using Scratch, the project player might turn blank, but as far as I'm aware it shouldn't cause the entire page to be unresponsive. It sounds like the project player keeps crashing while you're casually using Scratch.
0 Comments
Leave a Reply. |