Logos 5 crash Error ID: 7196 InvalidOperationException: Invoke or BeginInvoke cannot be called on a

John Salinas

This is not the first time I have seen this crash so it seemed good to report it.  I see this crash when I have a lot of resources open and I go away from the computer for awhile (hours) and then come back and try to maximize logos to continue where I pick off.  Windows brings up a windows that says logos 5 has crashed and then I see: 

Windows is collecting more information about the problem. This might take several minutes ...

Files that help describe the problem:
C:\Users\perlturtle\AppData\Local\Temp\WER164D.tmp.WERInternalMetadata.xml
C:\Users\perlturtle\AppData\Local\Temp\WER310E.tmp.appcompat.txt
C:\Users\perlturtle\AppData\Local\Temp\WER6049.tmp.mdmp

Read our privacy statement online:
http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0409

If the online privacy statement is not available, please read our privacy statement offline:
C:\windows\system32\en-US\erofflps.txt

Here is the logos crash information: 

Data path: C:\Users\perlturtle\AppData\Local\Logos4\Data\zgckebeo.ezn
Free disk space: 287,959 MB
Temp path: C:\Users\perlturtle\AppData\Local\Temp\
Free temp space: 287,959 MB

Error ID: 7196
Error detail: InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.

System.InvalidOperationException: Invoke or BeginInvoke cannot be called on a control until the window handle has been created.
at System.Windows.Forms.Control.MarshaledInvoke(Control caller, Delegate method, Object[] args, Boolean synchronous)
at System.Windows.Forms.Control.BeginInvoke(Delegate method, Object[] args)
at System.Windows.Forms.Control.BeginInvoke(Delegate method)
at Libronix.Utility.Windows.GlobalHotKeys.Dispose()
at Libronix.Utility.DisposableUtility.Dispose[T](T& obj)
at LDLS4.GlobalHotKeysManager.Dispose()
at Libronix.Utility.DisposableUtility.Dispose[T](T& obj)
at LDLS4.AppModel.Dispose()
at LDLS4.OurApp.OnExit(ExitEventArgs e)
at System.Windows.Application.DoShutdown()
at System.Windows.Application.ShutdownImpl()
at System.Windows.Application.ShutdownCallback(Object arg)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Int32 numArgs)
at MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Windows.Threading.DispatcherOperation.Invoke()
at System.Windows.Threading.Dispatcher.ProcessQueue()
at System.Windows.Threading.Dispatcher.WndProcHook(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 MS.Internal.Threading.ExceptionFilterHelper.TryCatchWhen(Object source, Delegate method, Object args, Int32 numArgs, Delegate catchHandler)
at System.Windows.Threading.Dispatcher.LegacyInvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Int32 numArgs)
at MS.Win32.HwndSubclass.SubclassWndProc(IntPtr hwnd, Int32 msg, IntPtr wParam, IntPtr lParam)
at MS.Win32.UnsafeNativeMethods.DispatchMessage(MSG& msg)
at System.Windows.Threading.Dispatcher.PushFrameImpl(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.PushFrame(DispatcherFrame frame)
at System.Windows.Threading.Dispatcher.Run()
at System.Windows.Application.RunDispatcher(Object ignore)
at System.Windows.Application.RunInternal(Window window)
at System.Windows.Application.Run(Window window)
at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)
at LDLS4.OurApp.Main(String[] astrArgs)

Also see logs attached below

0358.LogosCrash.txt

63002.LogosError.log

2047.Logos4Error perlturtle-msi 2012.06.21 12.37.log

Any ideas on how I can avoid this would be very much appreciated. 

Dave Hooton

It seems to be an exceptional crash and you should avoid the situation you describe. Does the computer sleep whilst you are away?

If it happens again please upload logos.log before restarting Logos as this would be helpful to diagnose events leading up to the crash - you first have to enable permanent logging as per http://wiki.logos.com/Diagnostic_Logging.

John Salinas

https://community.logos.com/discussion/comment/488240#Comment_488240

No, my computer does not sleep in this situation (I currently have it setup not to sleep while it is plugged into an outlet).  What suggestions do people have for avoiding this situation -- such as how can I shutdown logos while I am away and bring it backup and have my groupings/link sets preserved and have it open back to the same spot in each my resources?  This would have to include the output of searches as well.  It is not uncommon for me to have need of the same set of resources of weeks and shutting down logos each time is a bit of pain.  Perhaps that is one thing books still have over computers  

Thanks, 

john 

Dave Hooton

https://community.logos.com/discussion/comment/488247#Comment_488247

John Salinas said:

What suggestions do people have for avoiding this situation -

Let the computer sleep

Create a Layout which will be saved when you exit and reloaded when you start. Note the Startup options in Tools >> Program Settings

Mike

Hello John,

The long string of "System.Windows" and "MS.etc,etc" may indicate that Logos is failing to load, access, or use a Microsoft component, likely some part of .NET. If you can provide a Logos.log of the error, this may help us troubleshoot this issue. If you can recreate the problem on demand, I'd strongly recommend calling in for direct support.

David Bailey

John Salinas said:

and then come back and try to maximize logos to continue where I pick off.  Windows brings up a windows that says logos 5 has crashed

Probably not related, but this reminds me of the Logos Blog bug that was reported some time ago...

David