Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

TDT 3.3.1 (beta) crashes on opening second instance #379

Open
shulist opened this issue Feb 11, 2019 · 1 comment
Open

TDT 3.3.1 (beta) crashes on opening second instance #379

shulist opened this issue Feb 11, 2019 · 1 comment

Comments

@shulist
Copy link

shulist commented Feb 11, 2019

Expected Behaviour: A second instance of TDT should open when the icon is selected.
Actual Behaviour: The app freezes and then crashes with the error message

An unexpected error ocurred Object reference not set to an instance of an object. Please see Help -> Show Error Log for more details

Error Log:

[2019-02-11 16:47:34] An unexpected error occurred
System.NullReferenceException: Object reference not set to an instance of an object.
   at Client.MainWindow.OnClosed(EventArgs e)
   at System.Windows.Window.WmDestroy()
   at System.Windows.Window.WindowFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at System.Windows.Interop.HwndSource.PublicHooksFilterMessage(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndWrapper.WndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam, Boolean& handled)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(Object o)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Int32 numArgs, Delegate catchHandler)
@shulist shulist changed the title TDT crashes on opening second instance TDT 3.3.1 (beta) crashes on opening second instance Feb 11, 2019
@caseydiers
Copy link

This appears to have been previously fixed as I use multiple instances regularly and have never run into this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants