Netplay.

[Mike Williams]

The calling thread cannot access this object because a different thread owns it.

App: LaunchBox
Version: 11.8
Type: System.InvalidOperationException
Site: Void VerifyAccess()
Source: WindowsBase

at System.Windows.Threading.Dispatcher.VerifyAccess()
at System.Windows.Window.get_CriticalHandle()
at System.Windows.Interop.WindowInteropHelper.get_CriticalHandle()
at System.Windows.Interop.WindowInteropHelper.get_Handle()
at Unbroken.LaunchBox.Windows.Desktop.MessageBoxEx.InterruptHttpRules(Object )
at Unbroken.LaunchBox.Windows.Desktop.MessageBoxEx.Show(Window ownerWindow, String text, String caption, MessageBoxButton buttons, MessageBoxImage icon, MessageBoxResult defResult)
at MethodParameter.NewHttpConfiguration(Window ownerWindow, String text, String caption, MessageBoxButton buttons, MessageBoxImage icon, MessageBoxResult defResult, MethodParameter )
at Unbroken.LaunchBox.Windows.Desktop.MessageBoxManager.ShowError(Window window, String error)
at ConsumerParameter.NewHttpConfiguration(Window window, String error, ConsumerParameter )
at Unbroken.LaunchBox.Windows.Desktop.ViewModels.RetroarchNetplayViewModel.ForgotDrivenError()
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.CustomizeFocusAccount(Object )
at Unbroken.LaunchBox.Windows.Threading.<>c__DisplayClass0_0.InterruptMetaDefinition()
at System.Threading.ThreadHelper.ThreadStart_Context(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
--- End of stack trace from previous location where exception was thrown ---
at System.Threading.ThreadHelper.ThreadStart()

Recent Log:

21:51:53 Exception

[Christian]

Could you walk me through what you were doing when you got this error message?

[Mike Williams]

right clicked sensible soccer ( PS1) and pressed start netplay. sensi works fine btw.

[Christian]

It happen every time you do it with that title?

[Mike Williams]

To be honest i think it was just a random thing, it seems to work fine now.

[Christian]

Yeah, this error happens because of threading which can make the error REALLY spotty. I’ll leave the ticket open for now because there probably is something somewhere that needs tweaked even though you aren’t consistently seeing the issue.