Flash / IE memory error?
Has anyone come across this error in testing their Flash applications?
The instruction at "0x01203e8d" referenced memory at "0x01203e8d".
The memory could not be "read".
It's been a frustrating bug to address. The actual memory address changes from time to time. I'm only able to reproduce this on a few machines at the office and it only occurs after the browser has been exited. I've been able to reduce the frequency of the error by re-working some sound objects that had "onComplete" handlers, but I'm still seeing this after I've played an FLV in the application. It seems like something that the application has done, doesn't mesh well with IE shutting down, cleaning out the activex objects, etc, who knows.
I originally thought it was tied to some bad sounds or bad FLV's, but I've tried the same media files in other swf's and haven't been able to reproduce the error. I also have gotten the error when I didn't play any FLV's at all, but was using an "onComplete" event like I said above.
It's been a fun Friday, commenting out code, ripping parts of the app out in an effort to locate what strange combination of events is causing this...
Curious if anyone has had any recent experience with something similar. I've googled of course, but only found some older references to similar issues. Figured a plea post for help might be worthwhile.
Tim Walling
Co-Founder at Connected Sports Ventures
blog@timwalling.com
