[fixed] ServerAsAServiceSettings branch: Client crash because of UnhandledException (1 Viewer)

[chefkoch]

full logs are attached

It happens immediately after Client GUI is being displayed and ready.
On a second try I was not able to reproduce it, but with another build previously I noticed it as well.

Here is the client exception:

[2013-03-13 03:57:37,556] [28624  ] [AMQ 'SettingsChangeWatcher`1'] [ERROR] - ApplicationLauncher: Unhandled exception in application
System.ObjectDisposedException: Das SafeHandle wurde geschlossen.
  bei System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
  bei System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext)
  bei System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout, Boolean exitContext)
  bei System.Threading.WaitHandle.WaitOne(Int32 millisecondsTimeout)
  bei MediaPortal.Common.Messaging.AsynchronousMessageQueue.DoWork()
  bei System.Threading.ThreadHelper.ThreadStart_Context(Object state)
  bei System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
  bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
  bei System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
  bei System.Threading.ThreadHelper.ThreadStart()

 

[morpheus_xx]

I've seen this issue as well, but I though it is fixed already in this commit: https://github.com/MediaPortal/MediaPortal-2/commit/b69ca963105cc97bd39fa866b2ed3d87c251cf02

Seems I need to check the termination sequence again, as my fix only addressed double disposal

 

[morpheus_xx]

Should be fixed now

 

[chefkoch]

Checked various scenarios and was not able to reproduce it anymore.

In case there is any issue again, thread can be reactivated.