Crash on startup

HJ. van der Wal

Logos 8.1 keeps crashing on startup. I have tried to work offline but even then the program quits when opening the home page. 

8664.LogosCrash.zip

Dave Hooton

As a temporary workaround, start Logos with CTRL key held and login (you will start with a blank layout).

You can alter startup preference in Program Settings to avoid the crash with Notes  e.g. a layout that doesn't have Notes.

HJ. van der Wal

https://community.logos.com/discussion/comment/1021345#Comment_1021345

Shalom Dave!

Thank you for taking time to answer me. However, I am afraid my problem is more than just a faulty layout. Once the startup tune sounds Logos quits working and disappears. Working offline (CTRL key) or online does not make any difference.

Dave Hooton said:

a layout that doesn't have Notes.

I hardly ever take notes although I do use highlighting. All of my custom layouts are without a note panel.

Just to be clear: I always use the default startup settings (i.e. homepage/dashboard).

HJ. van der Wal

https://community.logos.com/discussion/comment/1021545#Comment_1021545

In the meantime the error has spread to my desktop computer and an older laptop (both of them running Windows 10).

I have discovered that the crash is not connected to Logos 8.1:

My other laptop had not been used for several months. It was still running Verbum 7.12 and I did not experience any problems. As a precaution I changed the startup setttings to a blank layout instead of the homepage. The next step was that I installed the latest Verbum 7 software (i.e. Verbum 7.19). After the first time Verbum also would not open anymore due to the same error.

Program Version: 7.19 (7.19.0.0009)
Windows Version: 10.0.17134.0
.NET Framework Version: 4.0.30319.42000
Time: 2018-12-17 09:57:04 +01:00 (2018-12-17T08:57:04Z)
Installed memory: 3,577 MB
Install path: C:\Users\HJ\AppData\Local\Verbum\System\Verbum.exe
Free install space: 207,731 MB
Data path: C:\Users\HJ\AppData\Local\Verbum\Data\ch2svuyu.ecu
Free disk space: 207,731 MB
Temp path: C:\Users\HJ\AppData\Local\Temp\
Free temp space: 207,731 MB

Error ID: 4654
Error detail: ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: nLength

System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
Parameter name: nLength
   at Libronix.DigitalLibrary.Resource.CreateTextRangeFromIndexedOffset(Int32 nOffset, Int32 nLength)
   at Libronix.DigitalLibrary.NotesTool.NotesToolManager.NotesDigitalLibraryService.<GetTextRangeBatchAsync>g__tryGetTextRangeResponse|4_2(TextRangeRequest item)
   at Libronix.DigitalLibrary.NotesTool.NotesToolManager.NotesDigitalLibraryService.<GetTextRangeBatchAsync>d__4.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.ValidateEnd(Task task)
   at Faithlife.NotesApi.ClientData.SqliteNotesClientRepository.<UpdateAnchorsAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Faithlife.NotesApi.Core.CommonNotesApi.<UpdateAnchorsAsync>d__18.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Faithlife.NotesApi.ClientCore.ClientNotesApi.<UpdateAnchorsAsync>d__23.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Libronix.DigitalLibrary.NotesTool.NotesToolManager.<UpdateAnchorsAsync>d__10.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at Libronix.DigitalLibrary.NotesTool.NotesToolManager.<<UpdateAnchors>b__8_0>d.MoveNext()

Dave Hooton

https://community.logos.com/discussion/comment/1021548#Comment_1021548

Please contact Customer Services for further assistance.

Ed Ball (Logos)

Thanks for the error logs! Two notes on Nelson’s Bible Map Collection seem to be the problem; we may have a bug with taking notes on that resource. Hopefully we get can a fix out quickly.

Ed Ball (Logos)

https://community.logos.com/discussion/comment/1022453#Comment_1022453

I removed the corrupt part of those two notes from our server, but I don't know if they will be downloaded to your application before it crashes. Let us know if it helped.

Ed Ball (Logos)

https://community.logos.com/discussion/comment/1022463#Comment_1022463

I'm taking notes on Nelson's Bible Map Collection but I haven't been able to recreate the bug. If you remember any details about how those two notes were created, please let us know.

The crash itself should be fixed with the next update to Logos 8.1.