|My website gives error in IE8|
My website gives error in IE8. IE crashes.
| 6:09 pm on Feb 9, 2011 (gmt 0)|
When I open my website on IE8, IE crashes.
To mention I've a flash object on my website. Can anyone please help me to solve this problem?
It gives the following error:
Problem Event Name:APPCRASH
Fault Module Name:Flash9f.ocx
Fault Module Version:188.8.131.52
Fault Module Timestamp:47e8643e
Additional Information 1:0a9e
Additional Information 2:0a9e372d3b4ad19135b953a78882e789
Additional Information 3:0a9e
Additional Information 4:0a9e372d3b4ad19135b953a78882e789
Read our privacy statement online:
If the online privacy statement is not available, please read our privacy statement offline:
Your help will be highly appreciated.
| 5:16 pm on Feb 10, 2011 (gmt 0)|
Well, here is how I would go about debugging this.
First I'd attempt to re-install the Flash plugin for IE.
If that didn't fix it, I'd create the simplest flash object possible - just type the word "test" in an .fla, export it as .swf, drop it in place on the page instead of the current Flash, run it.
If it still crashes, not sure what I'd do at that point, but I am guessing it won't.
If it doesn't crash, this means there is something within the Flash that is causing an error; either it's programmed inefficiently, using up too much memory or getting into an infinite loop, or it's requesting resources that don't exist, such as eternal ActionScript modules that aren't in place.
Flash is not inherently "real smart" that way - one example is if you import external objects, such as images in a slide show, and you reference them incorrectly (i.e., pointed to a file that doesn't exist,) your browser will hang there" waiting for example.com . . . " and never time out. The programmer has to program in error traps for these conditions, and many don't.
Another possibility is if this works in other browsers and only crashes in IE, given that your "test flash" works fine, it's possible the Flash is trying to do something IE specific and can't communicate with the page due to some fault in the Flash programming in identifying the browser, or something along those lines.
What this internal Flash condition could be, can't say. You'd have to get in and start debugging it from within the .fla.