Flash / IE memory error?
March 10th, 2006
Has anyone come across this error in testing their Flash applications?
The instruction at “0×01203e8d” referenced memory at “0×01203e8d”. 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.
buy levitra
buy levitra online
cheap levitra
discount levitra
generic levitra
levitra canada
levitra com
levitra comparison
levitra dosage
levitra drug
levitra info
levitra information
levitra on line
levitra online
levitra pharmacy
levitra pills
levitra prescription
levitra prices
levitra sales
levitra side effects
levitra vardenafil
order levitra
bayer levitra
levitra 10 mg
levitra 10mg
levitra 20 mg
levitra 20mg
levitra alcohol
levitra dose
levitra duration
levitra medication
levitra pill
levitra prescribing information
levitra review
levitra samples
levitra stories
levitra tablets
levitra without prescription
levitra no prescription
purchase levitra
side effects of levitra
about levitra
levitra from canada
levitra side affects
meridia
buy meridia
buy meridia cheap
buy meridia online
cheap meridia
discount meridia
generic meridia
meridia com
meridia coupon
meridia diet
meridia diet pill
meridia drug
meridia hospital
meridia online
meridia order
meridia phentermine
meridia pill
meridia prescription
meridia side effects
meridia weight loss
pharmacy meridia
cheapest meridia
does meridia work
how does meridia work
meridia 10 mg
meridia 10mg
meridia 15 mg
meridia 15mg
meridia blog
meridia canada
meridia cost
meridia credit union
meridia diet drug
meridia diet pills
meridia dosage
meridia effectiveness
meridia health system
meridia information
meridia iud
meridia manufacturer
meridia medication
meridia mexico
meridia no prescription
meridia on line
meridia pills
meridia price
meridia reductil
meridia reviews
meridia sibutramine
meridia success
meridia testimonials
meridia vs phentermine
meridia weight loss drug
meridia weight loss medication
meridia weight loss pill
meridia weight loss pills
meridia without prescription
order meridia online
purchase meridia
what is meridia
about meridia
Currently residing in Scituate, MA and working at 
March 10th, 2006 at 10:30 pm
I got the same problem but didn’t figure out what is going on yet. It might be some programs + flash + ie combination because it happens with me with any flash website and to get rid of this problem I just logoff and then login again.
It’s weird because it never happened on my home PC (same swf, same websites) so I guess it should be my office PC problem.
March 10th, 2006 at 11:32 pm
Yes, I’v got same alert too.
March 11th, 2006 at 12:13 am
I’ve encountered the same problem on a number of occasions on different machines, but have never been able to identify the cause of the issue. I think part of the problem is that it doesn’t seem to occur consistently.
April 24th, 2006 at 11:32 am
Have been stuggling with this all day. Like you i thought it was a problem with my code etc. Turns out it is infact a problem with ie, your user mode (permissions) and flash. This is why it only occurs at work, where i have restricted permissions. I realise now that I can replicate the error on any flash movie. All i have to do is click on it before closing IE and i get the error. Could be something to do with that recent windows update which changes the way IE handles active x content. But i’m not sure. Do you have any joy finding a fix?
August 31st, 2006 at 5:48 am
It also happened to one of my programs. But it’s an exe file, not a swf file, so I don’t think it’s relating to how IE handles ActiveX. The frustrating part is that this happened to my client and I can’t seem to replicate it on my machines. Did anyone try to see if it’s occuring on Flash Player 8 too?
September 21st, 2006 at 12:50 pm
I’ve got the same problem. And I did a windows update recently…..
I’m also using flash 8….
February 8th, 2007 at 4:53 pm
hi guys.
ok i have had this problem for a while.
ive tried everything for malware to spyware….etc
its a conflict wiith ie and software….
i am running windows xp ….. now working on the updates.
until i hadthe updates i had no problem.
will let u know.
February 20th, 2007 at 8:38 pm
had this problem too. was surfing in youtude when that suddenly happened.. nw both my mozilla and IE can’t load any pages.. but my games like WoW and Steam still works fine.. anyone has any tips on solving this problem?
March 5th, 2007 at 7:28 am
I’m experiencing the same behavior on my site. FF-OK, IE takes a dump. I have some embedded movies (flash) a ‘Wimpy’ music player plugin (flash) and I disabled each of them, rebooted and I still have the same problem. Anyone? Bueller?
March 6th, 2007 at 11:14 am
In IE7:
Tools > Internet Options > Advanced (tab)
- Restore Advanced Settings
- Reset Internet Explorer Settings
Although this defaults your IE7 as if you’ve never used it before, I’ve found that my problem has gone away.
March 6th, 2007 at 11:19 am
Well that’s that first time I’ve seen a way to make it go away. Last time I encountered this (which was when I blogged about it) we never really found a way to get around it. It just seems like one of those IE errors that you can’t really predict and have to live with.