Flash9b.ocx crash once again

FYI
I have escalated this to our Adobe Technical Account Manager, who has already been in touch collating relevant information.
I shall post anything relevant.

Well, not to let Adobe completely off the hook, but IE is also a problem.
Due to specifications rules set out by our client, our application is only "guaranteed" to work on IE 6 for our clients.
Well, after extensive testing, IE 6 (and probably 7) has several memory leaks when combined with Javascript. I think we all know that IE's javascript functionality is poor at best.
We contacted Microsoft as well as Adobe and MS basically told us, "anything could go wrong with a leak like this--and we will fix it eventually--but since we don't make Flash Player, we can't help you with your application."
So basically, until Microsoft fixes IE 6, there is still a limit to how much Adobe can do to make Flash player work. A house built on a bad foundation, no matter how well built, is still unstable. And developing stuff for IE is quite frankly like building a house on top of a marsh.

Now, what Adobe fails to do is to make this clear to people who have to make applications. Why? Maybe because Microsoft is now competing with their own Silverlight RIA tool. You can bet that if Silverlight didn't work, Microsoft would do something about it since its theirs. Now Flash Player is their competitor, so I doubt Microsoft cares about fixing IE just so their competitor's application will work. Adobe obviously would never want to admit this. Adobe's answer? AIR, I presume.

Finally, the only think I feel obliged to take Adobe to task for is that everytime they release a new player, they GUARANTEE that legacy applications will still work. This guarantee is fallacious. With FP 9 the memory management has changed such that it is exposed to vulnerabilities and instabilities in IE 6's own memory management where previously it was not. So, although in a "perfect world" legacy applications for say, FP 7 should work in FP 9, in reality, they do not. I also understand that it is unrealistic to expect Adobe and MS to cooperate since they are now competitors, but I really really wish Adobe would stop making these stupid guarantees regarding Flash Player and MIE that prompt users to update their flash player and then, by so doing, destabilize legacy applications. Adobe does not suffer from the repurcussions directly. Who does? The application developer. With FP 9's release, suddenly our client is barraging us with complaints that our application does not work. Obviously, if they hadn't updated FP 7 to FP 9 in the first place, then our application would be fine. But then again, THEY are the CUSTOMER and they only updated because, like I said, Adobe GUARANTEED that contents made in AS 2.0 would work in FP 9. Thanks a hell of a lot, Adobe.

The solution? Unfortunately there is none for us with our legacy applications. We have to admit to our client that we cannot support the application we made for them. If there's a lawsuit, well, there is a lawsuit and you better believe Adobe will be hearing from us--but I doubt it will come to that. We have to simply learn from this horrible experience and move on. From now on, if our clients want us to make content to run in IE then our response has to be to use Silverlight. No more Flash. If they want us to make contents in Flash then our response has to be use AIR. No more IE. That is the only way to guarantee stability, or at the very least, guarantee a responsible response from either proprietor.

In conclusion:
Adobe Technology + Microsoft Technology = misery.

Hello !
Iv'e been plagued with this ocx crash in both XP Pro and Vista flash9c.ocx or flash9d.ocx 00000005 appcrash.
Think I finally have found the cure and should share it here.

In Vista it seems flashplayer install creates a bogus registry entry at :
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\TypeLib\{57A0E746-3863-4D20-A811-950C84F1DB9B}\1.1\0\win32
Vaulue i had in a completely new Vista (fresh) install and activeX install from adobe website was
C:\Windows\system32\Macromed\Flash\Flash9d.ocx\2

String ends up pointing to a directory 2 (which of course is non existing)

String changed to
C:\Windows\system32\Macromed\Flash\Flash9d.ocx
And all crashing has stopped.

It's the same with XP - string ends with directory 2
But classes typelib was another

To check - do a search in registry (Vista or XP) for the word/key flash9d.ocx and when the flash9d.ocx\2 string comes up
modify it.Locations may differ - if it comes up with \2 ANYWHERE modify it to :
C:\Windows\system32\Macromed\Flash\Flash9d.ocx,2
or just
C:\Windows\system32\Macromed\Flash\Flash9d.ocx


I'm guessing it should perhaps be a parameter like e.g C:\Windows\system32\Macromed\Flash\Flash9d.ocx,2
But leaving it like "C:\Windows\system32\Macromed\Flash\Flash9d.ocx" works now fine for me.

- Syar -

nope, I have 2 gigs of RAM and it crashes all the time

just wanna say that i had huge problems with youtube crashing and showing ie and flash error until i installed the beta flash version and plugin for ie looks like its finally working no errors yet and ie dont die like before every 2 minutes i hope this works for every one to:)

ive installed the first two
http://labs.adobe.com/downloads/flashplayer9.html