BUG: Reproducible crash in Exegetical Guide
When choosing Scrivener's 1881 in the Word-by-Word section of the Exegetical Guide I get a crash. I haven't finished indexing yet, in case that's the cause. But obviously even if it is, Logos should handle it more gracefully.
2009-12-19 23:42:17.8523 13 Warn KeyLinkManager Matched override reference gnt/276 in LLS:46.30.4 but there were no corresponding milestones for the headword/reference.
2009-12-19 23:42:19.8384 7 Warn LibraryCatalog No metadata found for resource 'LLS:AV1873'.
2009-12-19 23:42:19.8584 7 Error OurApp Unhandled exception: System.ArgumentNullException: Value cannot be null.
Parameter name: resource
at Libronix.DigitalLibrary.KeyLinkManager.FindBestMilestones(Resource resource, ResourceMilestoneQuery query)
at Libronix.DigitalLibrary.Guides.Sections.WordByWordSection.<DoUpdateTextStandardResource>d__50.MoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution()
at Libronix.Utility.Threading.AsyncAction.Continue()
at Libronix.Utility.Threading.ThreadPoolAsyncAction.<Start>b__0(Object )
at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
at System.Threading._ThreadPoolWaitCallback.WaitCallback_Context(Object state)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
Comments
-
Just for more data:
I didn't get the error and I'm not indexing.
Win 7 OS
Robert Pavich
For help go to the Wiki: http://wiki.logos.com/Table_of_Contents__
0 -
And for even more data, I've finished indexing and still get the crash!
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
OK, I think I know the problem. I think it's because I've hidden the Cambridge Paragraph Bible. Switching to Scriveners on the Greek tries to switch to Cambridge on the right, and because I don't have it, it crashes.
I've hidden Cambridge, because I don't need it if I have KJV (1900), do I?
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
OK, I think I know the problem. I think it's because I've hidden the Cambridge Paragraph Bible. Switching to Scriveners on the Greek tries to switch to Cambridge on the right, and because I don't have it, it crashes.
I've hidden Cambridge, because I don't need it if I have KJV (1900), do I?
I get NKJV on the right, not Cambridge (nor KJV1900)!?
Dave
===Windows 11 & Android 13
0 -
Interesting. When I unhide Cambridge, and choose Scrivener, it is indeed Cambridge that appears on the right. It's definitely Scrivener's 1881 you're trying it with? Anyway, with Cambridge unhidden there's no crash. With it hidden there is, so that's definitely the problem.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark Barnes said:
OK, I think I know the problem. I think it's because I've hidden the Cambridge Paragraph Bible. Switching to Scriveners on the Greek tries to switch to Cambridge on the right, and because I don't have it, it crashes.
I've hidden Cambridge, because I don't need it if I have KJV (1900), do I?
Thanks for reporting this; that is the cause of the problem.
The AV1873 is currently specified as the preferred surface text for Scrivener 1881; at the moment, it appears that the code can't fall back to using the KJV 1900.
0
