Logos 7 Layout Crashes

Kevin M. Adams
Kevin M. Adams Member Posts: 35 ✭✭
edited November 2024 in English Forum

Under Saved Layouts (L7) my James Layout crashes Logos regularly (multiple times per day) causing great frustration in using this layout and studying for sermons and bible prep.

5327.Logos Log Files 120316 KMA.zip

Comments

  • JT (alabama24)
    JT (alabama24) MVP Posts: 36,523

    Have you tried rebuilding it? 

    macOS, iOS & iPadOS |Logs| Install
    Choose Truth Over Tribe | Become a Joyful Outsider!

  • Kevin M. Adams
    Kevin M. Adams Member Posts: 35 ✭✭
    https://community.logos.com/discussion/comment/868647#Comment_868647

    alabama24 said:

    Have you tried rebuilding it? 

    No I have not. I thought the latest update fixed the layout bugs?? Since there are a lot of resources open and synced in this layout it would take me a bit to re-create it (I'm guessing that is what you mean - make a new one and delete the old one). Is there a quicker way to sync books (link sets) than individually clicking on them and selecting the link set desired? 

  • Dave Hooton
    Dave Hooton MVP Posts: 36,192
    https://community.logos.com/discussion/comment/868673#Comment_868673

    Kevin M. Adams said:

    No I have not. I thought the latest update fixed the layout bugs??

    Only where a search was conducted in the presence of the Bible Browser tool (and there is no evidence of a crash in your logs).

    Looking at two resources with format errors - The Bible Exposition Commentary and Believer's Bible Commentary - they are older versions than mine. It would be worthwhile checking for newer resources with the command update resources. Please ensure logging is enabled before doing this so we can diagnose any issues.

    EDIT: These are saved text ranges, probably from your Notes. You could still do the check, though.

    Kevin M. Adams said:

    Since there are a lot of resources open and synced in this layout it would take me a bit to re-create it (I'm guessing that is what you mean - make a new one and delete the old one). Is there a quicker way to sync books (link sets) than individually clicking on them and selecting the link set desired? 

    This was the intention, but hold off until you update resources. You can use the multi-view feature if you have a Logos/Verbum Now subscription, but I doubt it would save time!

    Dave
    ===

    Windows 11 & Android 13

  • Kevin M. Adams
    Kevin M. Adams Member Posts: 35 ✭✭
    https://community.logos.com/discussion/comment/868721#Comment_868721

    Dave Hooton said:

    checking for newer resources with the command update resources.

    I've done this and it says  everything is synchronized and up to date

    I've opened L7 with logging enabled (ctrl + open program) and it crashed after about 5 minutes of use. File attached.

    Kevin0245.Logos Log Files 120316b KMA.zip

  • Dave Hooton
    Dave Hooton MVP Posts: 36,192
    https://community.logos.com/discussion/comment/868734#Comment_868734

    It's crashing too fast for Logos, so we need the Windows Event Viewer

    Dave
    ===

    Windows 11 & Android 13

  • Kevin M. Adams
    Kevin M. Adams Member Posts: 35 ✭✭
    https://community.logos.com/discussion/comment/868766#Comment_868766

    Dave Hooton said:

    It's crashing too fast for Logos, so we need the Windows Event Viewer

    There appears to be an Application Error and a .NET Runtime error. This is the copy and paste for the General tab for the Application error

    Faulting application name: Logos.exe, version: 7.2.0.38, time stamp: 0x583352e4
    Faulting module name: Libronix.DigitalLibrary.Resources.Native.dll, version: 7.2.0.38, time stamp: 0x58335264
    Exception code: 0xc0000005
    Fault offset: 0x000000000015bb20
    Faulting process id: 0xd70
    Faulting application start time: 0x01d24e8e4107287b
    Faulting application path: C:\Users\KMA\AppData\Local\Logos5\System\Logos.exe
    Faulting module path: C:\Users\KMA\AppData\Local\Logos5\System\Libronix.DigitalLibrary.Resources.Native.dll
    Report Id: 1c196bf1-7e4c-4708-a8de-077301d24b2f
    Faulting package full name:
    Faulting package-relative application ID:

    And this is for the .NET Runtime error

    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.MarkupApplierWrapper_ApplyMarkup(Libronix.DigitalLibrary.Resources.Logos.SafeMarkupApplierWrapperHandle, Libronix.DigitalLibrary.Resources.Logos.SafeTextInsertMarkupCacheHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElementMarkupHelper.OnOffsetRangeLoaded(Int32, Int32)
    at Libronix.DigitalLibrary.Resources.Logos.NativeMethods.LogosDisplayState_ReloadAtCurrentPosition(Libronix.DigitalLibrary.Resources.Logos.SafeLogosDisplayStateHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElement.OnReloadContent()
    at System.Windows.Threading.DispatcherTimer.FireTick(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 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.Threading.SingleInstanceManager)
    at LDLS4.OurApp.Main(System.String[])

  • Kevin M. Adams
    Kevin M. Adams Member Posts: 35 ✭✭
    https://community.logos.com/discussion/comment/868806#Comment_868806

    Here are additional Errors from couple days prior - not sure if they are needed or not but since I'm here I figured I'd post them in case they are needed.

    Faulting application name: LogosCEF.exe, version: 1.5.0.0, time stamp: 0x5812839a
    Faulting module name: libcef.dll, version: 3.2704.1431.0, time stamp: 0x57644782
    Exception code: 0xc0000005
    Fault offset: 0x0000000000387d95
    Faulting process id: 0x3dac
    Faulting application start time: 0x01d24dc7487804e2
    Faulting application path: C:\Users\KMA\AppData\Local\Logos5\System\LogosCEF.exe
    Faulting module path: C:\Users\KMA\AppData\Local\Logos5\System\libcef.dll
    Report Id: eec56b02-69e8-4887-ba35-72a4311959e2
    Faulting package full name:
    Faulting package-relative application ID:

    Faulting application name: Logos.exe, version: 7.2.0.38, time stamp: 0x583352e4
    Faulting module name: Libronix.DigitalLibrary.Resources.Native.dll, version: 7.2.0.38, time stamp: 0x58335264
    Exception code: 0xc0000005
    Fault offset: 0x000000000015bb20
    Faulting process id: 0x1d40
    Faulting application start time: 0x01d24dc73cf89f52
    Faulting application path: C:\Users\KMA\AppData\Local\Logos5\System\Logos.exe
    Faulting module path: C:\Users\KMA\AppData\Local\Logos5\System\Libronix.DigitalLibrary.Resources.Native.dll
    Report Id: 289b9b5d-07b6-4c21-ae0b-cef33fe22726
    Faulting package full name:
    Faulting package-relative application ID:

    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.MarkupApplierWrapper_ApplyMarkup(Libronix.DigitalLibrary.Resources.Logos.SafeMarkupApplierWrapperHandle, Libronix.DigitalLibrary.Resources.Logos.SafeTextInsertMarkupCacheHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElementMarkupHelper.OnOffsetRangeLoaded(Int32, Int32)
    at Libronix.DigitalLibrary.Resources.Logos.NativeMethods.LogosDisplayState_ReloadAtCurrentPosition(Libronix.DigitalLibrary.Resources.Logos.SafeLogosDisplayStateHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElement.OnReloadContent()
    at System.Windows.Threading.DispatcherTimer.FireTick(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 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.Threading.SingleInstanceManager)
    at LDLS4.OurApp.Main(System.String[])

    Faulting application name: LogosCEF.exe, version: 1.5.0.0, time stamp: 0x5812839a
    Faulting module name: libcef.dll, version: 3.2704.1431.0, time stamp: 0x57644782
    Exception code: 0xc0000005
    Fault offset: 0x0000000000387d95
    Faulting process id: 0x43b4
    Faulting application start time: 0x01d24c8ecc110e05
    Faulting application path: C:\Users\KMA\AppData\Local\Logos5\System\LogosCEF.exe
    Faulting module path: C:\Users\KMA\AppData\Local\Logos5\System\libcef.dll
    Report Id: 1bc064e6-a826-4454-8f98-170d20dabdfa
    Faulting package full name:
    Faulting package-relative application ID:

    Faulting application name: Logos.exe, version: 7.2.0.38, time stamp: 0x583352e4
    Faulting module name: Libronix.DigitalLibrary.Resources.Native.dll, version: 7.2.0.38, time stamp: 0x58335264
    Exception code: 0xc0000005
    Fault offset: 0x000000000015bb20
    Faulting process id: 0x1ae0
    Faulting application start time: 0x01d24c8ec045e66e
    Faulting application path: C:\Users\KMA\AppData\Local\Logos5\System\Logos.exe
    Faulting module path: C:\Users\KMA\AppData\Local\Logos5\System\Libronix.DigitalLibrary.Resources.Native.dll
    Report Id: 55fd91ed-31a3-4257-9011-b4ff3acee035
    Faulting package full name:
    Faulting package-relative application ID:

    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.MarkupApplierWrapper_ApplyMarkup(Libronix.DigitalLibrary.Resources.Logos.SafeMarkupApplierWrapperHandle, Libronix.DigitalLibrary.Resources.Logos.SafeTextInsertMarkupCacheHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElementMarkupHelper.OnOffsetRangeLoaded(Int32, Int32)
    at Libronix.DigitalLibrary.Resources.Logos.NativeMethods.LogosDisplayState_ReloadAtCurrentPosition(Libronix.DigitalLibrary.Resources.Logos.SafeLogosDisplayStateHandle)
    at Libronix.DigitalLibrary.Resources.Logos.Controls.LogosDisplayElement.OnReloadContent()
    at System.Windows.Threading.DispatcherTimer.FireTick(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 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.Threading.SingleInstanceManager)
    at LDLS4.OurApp.Main(System.String[])

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,137

    This appears to be a native crash, so for Development to investigate further, we'll need a crash dump (captured with ProcDump). There are instructions at https://wiki.logos.com/ProcDump or you can contact Tech Support and reference this thread.

  • James Ogle
    James Ogle Member Posts: 77 ✭✭
    https://community.logos.com/discussion/comment/868833#Comment_868833

    I've been working through James (Greek Notes and such) as well and Logos crashes all the time. So this probably isn't an isolated issue. 

    Just though I would say something. 

  • Kevin M. Adams
    Kevin M. Adams Member Posts: 35 ✭✭
    https://community.logos.com/discussion/comment/868846#Comment_868846

    6724.ProcDoc Log 010617 continuous.docx4251.ProcDoc Log 010317b continuous.docx1121.ProcDoc Log 010317 continuous.docxI finally was able to get ProcDump to work (with Logos assistance). Logos doesn't crash if it's running but if it's not running Logos crashes, thus there are no ProcDump logs created in this situation. I copy and pasted some of the info from the Command Prompt. Please let me know if this info is beneficial. I had to do a clean install about 2 years ago (or less) bc Logos kept having problems and now it's impossible to use it without ProcDump running. Proclaim also is not right - refusing to update, constantly giving me messages that say update didn't install properly, etc. Tech's have spend an hour or two unable to figure out the problem. 4744.ProcDoc Log 12.31.16 before restart.docx

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 12,137
    https://community.logos.com/discussion/comment/875130#Comment_875130

    Kevin M. Adams said:

    Logos doesn't crash if it's running but if it's not running Logos crashes, thus there are no ProcDump logs created in this situation.

    I have no idea why running ProcDump would stop Logos crashing; that's very strange.

    I have one more idea, though.

    Launch an Administrator Command Prompt and enter:

    md C:\Dumps
    procdump -i C:\Dumps

    Then run Logos normally. When it crashes, has a Logos dump file been created in C:\Dumps? If so, please upload that to us.

    You can then run "procdump -u" to uninstall it and stop collecting crash dumps.

Categories