Exception of type System.​Execution​Engine​Exception was thrown.

"Exception of type System.ExecutionEngineException was thrown."
 This exception occurs when closing down an application of mine. Line 1203, right on "}" after the Main() method.... What's up?

something did not shutdown.

any worker threads running?

any async calls ?

any hung calls to the os?

what does the rest of the exception have?

inner stack trace?

how is the app closed?  from a GUI button or??

what version of .Net ? 1.0 1.1 2.0.xxx

figuerres wrote:

something did not shutdown.

any worker threads running?

any async calls ?

any hung calls to the os?

what does the rest of the exception have?

inner stack trace?

how is the app closed?  from a GUI button or??

what version of .Net ? 1.0 1.1 2.0.xxx

no.
no.

- $exception {System.ExecutionEngineException} System.ExecutionEngineException
- System.SystemException {"Exception of type System.ExecutionEngineException was thrown."} System.SystemException
- System.Exception {"Exception of type System.ExecutionEngineException was thrown." } System.Exception
 System.Object {System.ExecutionEngineException} System.Object
 _className "System.ExecutionEngineException" string
 _COMPlusExceptionCode -532459699 int
 _exceptionMethod <undefined value> System.Reflection.MethodBase
 _exceptionMethodString null string
 _helpURL null string
 _HResult -2146233082 int
 _innerException { } System.Exception
 _message null string
 _remoteStackIndex 0 int
 _remoteStackTraceString null string
 _source null string
 _stackTrace <undefined value> System.Object
 _stackTraceString null string
 _xcode -532459699 int
 _xptrs 0 int
 HelpLink null string
 HResult -2146233082 int
 InnerException { } System.Exception
 Message "Exception of type System.ExecutionEngineException was thrown." string
 Source null string
 StackTrace null string
 TargetSite <undefined value> System.Reflection.MethodBase

closed by hitting the X button on the bar.
1.1.4322

so then you have a COM Dll loaded thats not shuting down, folow the info.... what Com Interop are you using, what do the hresult and com exception code reveal when de-coded?

figuerres wrote:

so then you have a COM Dll loaded thats not shuting down, folow the info.... what Com Interop are you using, what do the hresult and com exception code reveal when de-coded?

no idea.
it leads back to the main starting point:

  [STAThread]
  static void Main() 
  {
   Application.Run(new frmMain());
  }

also, why am i getting a feeling that it is happening here?

public frmMain()
  {
  Thread th = new Thread(new ThreadStart(DoSplash));
  th.Start();
  Thread.Sleep(3000);
  th.Abort();
  Thread.Sleep(3000);
  InitializeComponent();
  Thread.Sleep(1000);
  }

Steve411 wrote:

public frmMain()   {   Thread th = new Thread(new ThreadStart(DoSplash));   th.Start();   Thread.Sleep(3000);   th.Abort();   Thread.Sleep(3000);   InitializeComponent();   Thread.Sleep(1000);   }

What is the DoSplash doing?  You can't do UI on different threads - all UI must be on the same thread that started the process.

Not if he does invokations in that thread.

Thats correct - lets just wait and see what DoSplash is doing.

You could try using CLR SPY and enabling the Customer Debug Probes, to see if anything is reported.

Show's a splash screen.

  public void DoSplash()
  {
   SplashForm Splash = new SplashForm();
   Splash.ShowDialog();
  }

Steve411 wrote:

Show's a splash screen.

public void DoSplash()   {    SplashForm Splash = new SplashForm();    Splash.ShowDialog();   }

change the above code to:

public void DoSplash()
  {
   //Do Nothing
  }

and see if the problem still  exists.  YOU ARE NOT ALLOWED to do UI on ANY OTHER THREAD other than the thread that created the process.

Still exists. Another thing, i removed the new thread code and it still exists, even though that thread was never started.

Buzza wrote:

YOU ARE NOT ALLOWED to do UI on ANY OTHER THREAD other than the thread that created the process.

Untrue. You should not change properties of UI on any thread other than the thread that created that form. It's acceptable to create forms on more than one thread - for example Internet Explorer basically has one thread per frame window.

So the thread was no problem at all. I am looking through the code right now and still can't find anything wrong...

Thanks for the help guys, Apperantly this was a known issue in .NET 1.1. It is fixed in the service pack!
 God Bless,
   Steve

Followup KB Article:
http://support.microsoft.com/kb/827210/