Crash everytime I check for program updates & start in debug mode

xriothhh

Beta Tester
It seems to be related to the system tray popup

I also have a 200MB .dmp file created with ProcDump if that is useful, and if there's a pdb / symbol file for AdGuard I could use it to debug with Visual Studio 2013 or WinDbg if needed (I feel more comfortable with the former). I'm not a developer but I do use both as diagnostic utilities.

The two relevant Event Viewer entries for the crash after checking program updates are date stamped "3/18/2015 9:48:21 AM"

And the two additional entries for the crash when starting in debug mode are datestamped "3/18/2015 9:57:54 AM"

It does sometimes start successfully in debug mode. I think the crash in this instance spawns sometimes because of the "Connection to server has been established" system tray notification:

The attached AdGuard log was after enabling detailed logging in AdGuard.

Both crashes have the same exception and .NET framework stack. Here's the stack itself for quick overview:
Code:
Stack:
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(System.Object)
   at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
   at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object)
   at System.Windows.Threading.DispatcherOperation.Invoke()
   at System.Windows.Threading.Dispatcher.ProcessQueue()
   at System.Windows.Threading.Dispatcher.WndProcHook(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndWrapper.WndProc(IntPtr, Int32, IntPtr, IntPtr, Boolean ByRef)
   at MS.Win32.HwndSubclass.DispatcherCallbackOperation(System.Object)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
   at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
   at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(System.Windows.Threading.DispatcherPriority, System.TimeSpan, System.Delegate, System.Object, Int32)
   at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr, Int32, IntPtr, IntPtr)
   at MS.Win32.UnsafeNativeMethods.DispatchMessage(System.Windows.Interop.MSG ByRef)
   at System.Windows.Threading.Dispatcher.PushFrameImpl(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.PushFrame(System.Windows.Threading.DispatcherFrame)
   at System.Windows.Threading.Dispatcher.Run()
   at System.Windows.Application.RunDispatcher(System.Object)
   at System.Windows.Application.RunInternal(System.Windows.Window)
   at System.Windows.Application.Run(System.Windows.Window)
   at Adguard.App.Main()
 

Attachments

Last edited by a moderator:

avatar

Administrator
Staff member
Administrator
Thank you!

This is UI process crash, not service, so we need to see logs from "agent" folder.
 

xriothhh

Beta Tester
I can't seem to reproduce the crash anymore after a reboot. I guess it was unrelated to AdGuard, probably some process hooking everything and causing corruption in memory or something like that.
 

avatar

Administrator
Staff member
Administrator
I can't seem to reproduce the crash anymore after a reboot. I guess it was unrelated to AdGuard, probably some process hooking everything and causing corruption in memory or something like that.
Maybe you're right because we can't reproduce it too.
 
Top