crash in secound screen

Issue #6932 resolved
Wagner Paiva created an issue

at ConnectionStub.FlushState(Object , String value, ConnectionStub )
at Unbroken.LaunchBox.Windows.BigBox.Data.OptionsListItem.Next()
at CallbackStub.FlushState(Object , CallbackStub )
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.OptionsListMenuItemViewModel.OnRight()
at ResolverStub.FlushState(Object , ResolverStub )
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.OptionsViewModel.OnRight(Boolean held, Boolean onlyRightPressed)
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.ComputeMap(Object , Boolean , Boolean )
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.OnRight(Boolean onlyRightPressed)
at AttributeStub.FlushState(Object , Boolean disposing, AttributeStub )
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.RegisterListener(Guid init)
at CodeAdapter.FlushState(Object , Guid asset, CodeAdapter )
at Unbroken.LaunchBox.Windows.BigBox.ViewModels.MainViewModel.<>c__DisplayClass345_1.SearchWrapper()
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.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading.ThreadHelper.ThreadStart()

Recent Log:

14:59:28 Exception

Comments (3)

  1. Christian

    Is this something you can make happen consistently, or does it appear to happen kind of randomly? If you can get the error to popup again could you copy the entire contents into the ticket? You’re missing a lot of the data from the top of the report which is pretty vital for tracking down what could be causing this.

  2. Wagner Paiva reporter

    It was a misconfiguration on the primary and secondary monitors in windows 11. Nvidia rearranged the order of the first screen and second screen. It's normal now.
    Thanks for your cooperation.

  3. Log in to comment