Adobe Flash plugin no longer supports processors without SSE???

Since Flash was released last December, the Flash plugin no longer fully supports my Pentium II 350. The plugin will crash on sites like and It will crash on and *if* you try to view the higher resolution version of the video.

The problem seems to be with the plugin trying to use an SSE instruction without checking if the processor actually supports it. When the instruction is not supported, the Flash plugin crashes and takes the browser with it.

The problem is present in both the ActiveX plugin and the Netscape plugin. This means that it will crash, Firefox, IE, Opera, Safari and any other browser that uses the plugin. What's worse is that was just released and it still has the problem.

It looks like Adobe is dropping support for non-SSE processors. If so, this would make them just as bad as Microsoft and its Silverlight plugin.

The Silverlight plugin initially worked fine on my PII, but they pulled the plugged on that when releasing the first final and now Silverlight won't even install. But, even if you workaround it, the plugin truly doesn't support non-SSE processors anymore and zero Silverlight sites work properly (the embedded plugin window will be blank). Safari Win32 actually didn't support non-SSE processors at first either, but they're cool and fixed it.

As a workaround, you can use Flash 9r47, but it has security holes. So, it's a toss-up between security and stability. However, a lot of sites are now requiring or newer to even work, so you might not have choice of stability.

Now, if you have a non-SSE processor, maybe it's time to upgrade (even an old PIII should do the trick). Or, maybe it's time to shift some tasks to one of your newer machines. However, I think that's besides the point. There are still zillions of users of non-SSE processors and just forgetting about them is not good (especially when the newest version of the plugin that works right has security flaws).

I think it's just a bug, but since users on the Flash player forums have been complaining and filing reports since came out and it still isn't fixed, I'm beginning to think it's intensional. I expect to see the Flash installer start saying "Processor not supported" on my PII machine before too long.

Maybe "Don't break the web!" should apply to the Silverlight and Flash plugins also!

7 Replies to “Adobe Flash plugin no longer supports processors without SSE???”

  1. @NoteMe: that doesn’t help if the browser itself (in this case the unpatched version of Safari) doesn’t support a processor.What’s a browser or even a plug-in developer doing writing processor support anyway? The programming environment should take care of such things automatically. Hmmm… maybe they were using a Microsoft manufactured programming environment and the teams who wrote and tested that environment never thought of testing it on old processors…

  2. that doesn’t help if the browser itself (in this case the unpatched version of Safari) doesn’t support a processor. n that case, you would not be able to surf the web at all with that browser on that cpu. If the browser supports old CPUs today, there is no reason why it should not have done so with the plug-ins integrated into the browser as long as it is the browser vendor who code the feature.The programming environment should take care of such things automatically.Lets just guess/assume Visual Studio was used in this case. Flash has been around for a while, but lets say they started out using VS6.0. Back then as far as I know VS did not take care of optimizing for SSE back then. Later on a processor pack came for VS6.0 and they could optimize for SSE. They wrote the code, and it has been hanging around since then, probably updated and maintained but not rewritten. “if it works, don’t fix it”. And that was until now. All this is just a wild guess though.- ØØ –

  3. Check the adobe thread above again. Thanks to wj89zgh for illustrating how to at least patch the plugin.Will just have to see if Adobe does anything about it.

  4. Glenn Drew writes:Hello, i also faced this error many times but i fixed it after reading this article . Hope someone might get help from this article

Leave a Reply

Your email address will not be published. Required fields are marked *