Getting strange InteropServices.SEHException exception

  • Thread starter Thread starter Tom Shelton
  • Start date Start date
T

Tom Shelton

I never get the above exception in Windows 2k. It only happens in
Windows XP, which is the first oddity. My application is multi-threaded and
I use the webbrowser control and media player. The exception normally occurs
when I open the browser control or media control, but sometimes it just
occurs randomly. I was thinking first that it was some sort of build
difference with the COM interop components, but I re-referenced and rebuilt
everything on an XP machine and that didn't help. I'm now thinking it's
some sort of multi-threading error. I don't know, I'm at a loss. If anyone
has experienced a similar problem and can provide me with some info. I will
greatly appreciate it.

Here's the full exception dump:

System.Runtime.InteropServices.SEHException: External component has thrown
an exception.
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMetho
ds+IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason,
Int32 pvLoopData)
at System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at MyApp.frmMain.Main() in C:\SoftwareDev\MyApp\MyApp
v5.0\SourceCode\MyApp\frmMain.cs:line 2901
Click to expand...

You wouldn't be updating the UI from a background thread would you? And
if you are, are you making sure your using .Invoke to do it?

Tom Shelton
 
I never get the above exception in Windows 2k. It only happens in
Windows XP, which is the first oddity. My application is multi-threaded and
I use the webbrowser control and media player. The exception normally occurs
when I open the browser control or media control, but sometimes it just
occurs randomly. I was thinking first that it was some sort of build
difference with the COM interop components, but I re-referenced and rebuilt
everything on an XP machine and that didn't help. I'm now thinking it's
some sort of multi-threading error. I don't know, I'm at a loss. If anyone
has experienced a similar problem and can provide me with some info. I will
greatly appreciate it.

Here's the full exception dump:

System.Runtime.InteropServices.SEHException: External component has thrown
an exception.
at System.Windows.Forms.UnsafeNativeMethods.DispatchMessageW(MSG& msg)
at
System.Windows.Forms.ComponentManager.System.Windows.Forms.UnsafeNativeMetho
ds+IMsoComponentManager.FPushMessageLoop(Int32 dwComponentID, Int32 reason,
Int32 pvLoopData)
at System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason,
ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at MyApp.frmMain.Main() in C:\SoftwareDev\MyApp\MyApp
v5.0\SourceCode\MyApp\frmMain.cs:line 2901
 
I removed the entry:

Application.EnableVisualStyles();

from my main function, and so far it seems to be more stable. I have a few
more tests to run, but I hope this nipped it in the bud.

Thanks,
Matt
 
Hi MJB, Do you have Application.DoEvents after
Application.EnableVisualStyles??

--
HTH,
-- Tom Spink, Über Geek

Please respond to the newsgroup,
so all can benefit

" System.Reflection Master "

==== Converting to 2002 ====
Remove inline declarations
 
I am getting the same problem. But I havent used
Application.EnableVisualStyles(); Specifically my error occurs on a return
from a dynamically created form, after a showdialog. Removing showdialog
removes the problem (but i dont know conclusively).
Thanks,
Hananiel
 
Back
Top