ProcMon at the time of crash)? I don't have expertise to go through such diagnostics so I'd like to avoid it unless it's likely to lead me to an answer about what I can do differently in my product or pinpoint an exact bug in the flash module (if there really is one). Is there any point trying to get a crash dump or other diagnostic information about the crash (e.g. and why would this not be a problem at dozens of other companies but be a problem at this one? Any thoughts on what could be the environmental factor that triggers the problem here but not on workstations set up differently? Is there anything I can try in my code/product that might avoid conflicting with Flash? For example, would rebasing my dlls to move my extension into a different area of memory have any hope of working? Would recompiling for. What I'm hoping for are some ideas about: And even if it is a Flash bug, from the customer's point of view that's no different from it being a bug in my product: either I get it fixed or my product will be uninstalled and they'll keep Flash. However, it's unlikely that the Flash team would investigate such a bug report unless I can point to something specific and replicable, and right now I can't replicate on any dev machines so that's not great. That leaves the possibility of a bug in Flash, which seems entirely possible, or a problem with the way I interact with the COM objects from IE.
Event id 1000 internet explorer 9 code#
No unmanaged code is being executed from my extension so it can't be that, so I can't think of anything my extension could do that could cause an AccessViolation. The faulting module being Flash32_13_0_0_214.ocx strongly points to it being a bug there but I suppose in theory it could be a problem in my code. If I disable Flash the problem goes away. If I disable my extension the problem goes away. NET 3.5 SP1, which isn't an ideal way to do it because of potential runtime conflicts with other extensions, but that's how it is for now.
Event id 1000 internet explorer 9 windows#
We tested after stopping all the windows services that mentioned Sophos and the same problem occurred so I'm fairly sure it's not related to that. Their workstations have Sophos antivirus running, and in some rare cases we've seen antivirus causing problems with our extension.
They've tried upgrading to the latest version but that had the same symptoms. This was a fairly new version of flash but not the latest. 16592, time stamp 0x544e95a7įaulting module name: Flash32_13_0_0_214.ocx, version 13.0.0.214, time stamp 0x5359c422įaulting application start time: 0x01d0099db319df49įaulting application path: C:\Program Files\Internet Explorer\iexplore.exeįaulting module path: C:\Windows\system32\Macromed\Flash\Flash32_13_0_0_214.ocx The windows application event log doesn't say much but it does say that the iexplore.exe process crashed with faulting module flash: Error / Application Error / EventID=1000įaulting application name: iexplore.exe, version. Either way it's frustrating! The user really doesn't care if the process crashes when they close the tab, so I'd be happy with a workaround that means no error message is shown to the user and the tab doesn't reopen. If the website is added to Trusted Sites then an error is written to the windows application event log and IE reopens the tab with a small info bar message saying IE recovered it from a crash. If the website isn't in Trusted Sites then the tab is running in Protected Mode and the result of the crash is a window saying the web page wants to run dw20.exe (i.e. some of my code still executes but very little. It still happens if my extension is configured to do nothing on that page - i.e. This only happens if both Flash and my extension are enabled and isn't replicable so far on workstations outside this company's environment. In one customer's environment we have a situation where when after visiting a website with Flash and closing the IE tab the tab process crashes. What can I try doing to avoid this clash? I have an Internet Explorer extension (a BHO) that works nicely on thousands of machines but in some scenarios seems to cause Flash to crash the iexplore.exe with an Access Violation.
0 kommentar(er)
