Logos crashes when clicking a link in the Notes & Highlights section of a resource
Logos crashes when I click a link in the Notes and Highlights section in the sidebar of a resource. No error message is given, literally just closes. This happens in both Windows and Macbook Pro
My computer: Macbook Pro with El Capitan OS. I also run a VM with Windows 7.
Logos 8.2
How to do it: Go to a resource, Bible for instance, and open the sidebar. Select the Notes & Highlights icon. Click on a link to narrow your search.
I would enclose a crash file, but the forum crashes when I try to attach a file, go figure.
Here is a little snippet of the crash file:
Process: Logos [372]
Path: /Applications/Logos 2.app/Contents/MacOS/Logos
Identifier: com.logos.Logos
Version: 8.2.0.15 (61902.0.15)
Code Type: X86-64 (Native)
Parent Process: ??? [1]
Responsible: Logos [372]
User ID: 501
Date/Time: 2019-01-25 22:03:26.387 -0500
OS Version: Mac OS X 10.11.6 (15G22010)
Report Version: 11
Anonymous UUID: D3A2666D-C39F-FF8F-4ECA-1B7DB1FA1077
Time Awake Since Boot: 310 seconds
System Integrity Protection: enabled
Crashed Thread: 0 CrBrowserMain Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_INVALID_ADDRESS at 0x0000000000000008
Exception Note: EXC_CORPSE_NOTIFY
VM Regions Near 0x8:
-->
__TEXT 0000000102607000-000000010260a000 [ 12K] r-x/rwx SM=COW /Applications/Logos 2.app/Contents/MacOS/Logos
Application Specific Information:
abort() called
Comments
-
I can reproduce in Windows.
I had filtered the ESV by Notes and clicked on Ecclesiastes under Bible Book. It has only one note, a Note by reference; which has several anchors and hyperlinks. A note by reference wasn't displayed for Matthew, but there are several other notes (by selection) which are displayed. Both notes by reference display normally in the full text of the resource.
It is a fast crash (repeatable) - so there is no crash/error log. Event Viewer log:
Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: System.AccessViolationException
at Libronix.DigitalLibrary.Resources.Logos.NativeMethods.LogosDisplayState_GetLoadedRegion(Libronix.DigitalLibrary.Resources.Logos.SafeLogosDisplayStateHandle, Libronix.DigitalLibrary.Resources.Logos.SafeLogosDisplayLoadedRegionHandle)
at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElement.OnUpdateVisibleRegion()
at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosContentDisplayElement.CheckNativeMacro()
at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosContentDisplayElement.OnRender(System.Windows.Media.DrawingContext)
at System.Windows.UIElement.Arrange(System.Windows.Rect)
at System.Windows.ContextLayoutManager.UpdateLayout()
at System.Windows.ContextLayoutManager.UpdateLayoutCallback(System.Object)
at System.Windows.Media.MediaContext.FireInvokeOnRenderCallbacks()
at System.Windows.Media.MediaContext.RenderMessageHandlerCore(System.Object)
at System.Windows.Media.MediaContext.AnimatedRenderMessageHandler(System.Object)
at System.Windows.Threading.ExceptionWrapper.InternalRealCall(System.Delegate, System.Object, Int32)
at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(System.Object, System.Delegate, System.Object, Int32, System.Delegate)
at System.Windows.Threading.DispatcherOperation.InvokeImpl()
at MS.Internal.CulturePreservingExecutionContext.CallbackWrapper(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 MS.Internal.CulturePreservingExecutionContext.Run(MS.Internal.CulturePreservingExecutionContext, 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 System.Windows.Threading.ExceptionWrapper.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.Application.RunDispatcher(System.Object)
at System.Windows.Application.RunInternal(System.Windows.Window)
at LDLS4.OurApp.InitializeAndRun(System.Collections.ObjectModel.ReadOnlyCollection`1<System.String>, Libronix.Utility.Windows.Threading.SingleInstanceManager, Libronix.Utility.Scope)
at LDLS4.OurApp.Main(System.String[])
1385.Logos.logDave
===Windows 11 & Android 13
0 -
Dave Hooton said:
t is a fast crash (repeatable) - so there is no crash/error log.
I can reproduce the same.
Have joy in the Lord!
0 -
We are working on a fix for this problem, which will be released in a future update.
0
