Crash when opening specific resource

This just started today and not sure why...hoping for a fix.

I regularly use "Drawing Near" as my morning devotional. Even have it as a shortcut .

Beginning today, when I try to open it...either by the shortcut OR via using the library, it crashes my Logos. Not sure why this started happening. Running the latest version Logos Bible Software 4.5c SR-2 (4.53.0.2280) and haven't had any recent updates either to Logos or Windows...and wondering why just this resource (that I've noticed) Any cure for this?

Thanks!

Donna Cole

Find more posts tagged with

Comments

Dave Hooton

Hello Donna,

We need to see some logs so please study http://wiki.logos.com/Diagnostic_Logging and attach logos4.log after a crash as described in http://wiki.logos.com/Uploading_Logs

Donna Cole

https://community.logos.com/discussion/comment/380798#Comment_380798

Hi Dave,

For whatever reason, when opening today... all was well. Go figure : )

I have copied the "error log" text below from the crash...and suspect it may have been a Win error and not a Logos error. Also, I did a complete re-indexing yesterday.

******LOGOS 4 ERROR LOG******************************

** Application Crash ***
Program Version: 4.5c SR-2 (4.53.0.2280)
Windows Version: 6.1.7601.65536
Time: 2012-07-08 17:05:30 -04:00 (2012-07-08T21:05:30Z)
Installed memory: 2,013 MB
Install path: C:\Users\Donna\AppData\Local\Logos4\System\Logos4.exe
Free install space: 57,595 MB
Data path: C:\Users\Donna\AppData\Local\Logos4\Data\5swsxrki.kmk
Free disk space: 57,595 MB
Temp path: C:\Users\Donna\AppData\Local\Temp\
Free temp space: 57,595 MB

Error ID: 3014
Error detail: AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.

System.AccessViolationException: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
   at LogosDisplayState.ReloadAtCurrentPosition(LogosDisplayState* )
   at Libronix.DigitalLibrary.Logos.LogosDisplayElement.OnReloadContent()
   at Libronix.DigitalLibrary.Logos.LogosContentDisplayElement.ReloadContent()
   at Libronix.Utility.Windows.DispatcherUtility.<>c__DisplayClassc.<CallSoon>b__b(Object , EventArgs )
   at System.Windows.Threading.DispatcherTimer.FireTick(Object unused)
   at System.Windows.Threading.ExceptionWrapper.InternalRealCall(Delegate callback, Object args, Boolean isSingleParameter)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.DispatcherOperation.InvokeImpl()
   at System.Windows.Threading.DispatcherOperation.InvokeInSecurityContext(Object state)
   at System.Threading.ExecutionContext.runTryCode(Object userData)
   at System.Runtime.CompilerServices.RuntimeHelpers.ExecuteCodeWithGuaranteedCleanup(TryCode code, CleanupCode backoutCode, Object userData)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state)
   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, Boolean isSingleParameter)
   at System.Windows.Threading.ExceptionWrapper.TryCatchWhen(Object source, Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.WrappedInvoke(Delegate callback, Object args, Boolean isSingleParameter, Delegate catchHandler)
   at System.Windows.Threading.Dispatcher.InvokeImpl(DispatcherPriority priority, TimeSpan timeout, Delegate method, Object args, Boolean isSingleParameter)
   at System.Windows.Threading.Dispatcher.Invoke(DispatcherPriority priority, Delegate method, Object arg)
   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 System.Windows.Application.Run()
   at LDLS4.OurApp.InitializeAndRun(ReadOnlyCollection`1 listArgs, SingleInstanceManager sim)
   at LDLS4.OurApp.Main(String[] astrArgs)

Thanks!

Donna Cole

Bradley Grainger (Logos)

Hi Donna,

Thanks for posting the crash log; unfortunately, I'm not able to identify the problem just from that information. It's possible that something about the text for today's reading is causing an issue for Logos. To test this theory, please enter the following command in the Command Box:

open drawing near to Jan 1

The program should display an option under "Resources" titled "Open Drawing Near—Daily Readings for a Deeper Faith to January 1". Click that option.

Does the resource open successfully to the entry for Jan 1st, or does it still crash? If it opens, you could try entering "July 10" in the location box in the resource panel to see if you can get to tomorrow's reading. If that works, there may just be something with the readings for July 7-9 that are causing a problem, but I don't exactly know what it would be. (I haven't been able to reproduce any problems scrolling through those readings.)

Donna Cole

https://community.logos.com/discussion/comment/380983#Comment_380983

Hi Bradley,

Thanks so much for your response. All appears to be working just fine now...I have "permanent logging" now so hope that should it occur again, I'll have more information for you. It was just plain wierd.

Donna Cole