BUG: L5 Crash Using BWS and LXX Swete

This crash is repeatable:

Steps:

1. Open BWS and enter a greek word (i.e οναι, καθαρισμός, etc) that is also found in the LXX

2. Run the report.

3. Under Textual Searches section, click on LXX to launch the Search - Morph results, using the search parameters shown.

4. Click on "Graph results"

I encountered this repeatable crash when I was trying to figure out how to display the frequency histogram using a non-English bible. I'm not sure how to accomplish this. I now know how to generate the histogram when L5 doesn't crash. Wished the histograms appear in the Textual Searches section as well as in Graph Bible Search Results.

Logs: 6064.Win7Pro64-Logos5-Crash-Log Files.zip

thanks,

David

Edit: The crash may also occur when using Logos LXX, Logos LXX ALT, and Lexham LXX bibles - depending on the greek word I think. For example, using the greek word for clean, pure (καθαρός), L5 crashes when using the Lexham LXX Int Swete Alt, but does not crash when using Lexham LXX Int Swete, Lexham LXX Int, and Lexham LXX Alt. Weird.

Find more posts tagged with

Comments

Mike

Hello David,

Thank you for reporting this. I am unable to reproduce the problem. It may be unique to your computer, possibly due to a corrupt database or index. Unfortunately, the Logos.log file you sent does not contain the crash, so I'm troubleshooting based only on the recorded callstack in your LogosError.log.

If you're open to it, I'd like to have you try the "Rebuild Index" command. This will likely take several hours, so you may wish to do this at night, before you go to bed.

If that does not resolve the issue, please let me know.

David Bailey

Hi Mike,

I'll try to re-index, probably tomorrow morning. Is this the crash?

Error ID: 9613
Error detail: InvalidCastException: Unable to cast object of type 'Libronix.DataTypes.NumericHierarchyReferencePoint' to type 'Libronix.DataTypes.Bible.BibleReference'.

System.InvalidCastException: Unable to cast object of type 'Libronix.DataTypes.NumericHierarchyReferencePoint' to type 'Libronix.DataTypes.Bible.BibleReference'.
   at LDLS4.Panels.GraphBibleSearchResultsPanel.Analyzers.ResultAnalyzer.GetBookReferenceRange(IEnumerable`1 seqSuperset, IEnumerable`1 seqFilterRange)
   at LDLS4.Panels.GraphBibleSearchResultsPanel.Analyzers.HitsInBookAnalyzer.GetReferenceRangeForResult(ReadOnlyCollection`1 referenceSupersets, ReadOnlyCollection`1 referenceRange)
   at LDLS4.Panels.GraphBibleSearchResultsPanel.Analyzers.ResultAnalyzer.AnalyzeResource(BibleReferenceResourceResult resource, LibraryCatalog libraryCatalog, ReadOnlyCollection`1 referenceRange, ResultAnalyzerOptions option, BibleDataType& dtBase, VersifiedResourceManager vrm)
   at LDLS4.Panels.GraphBibleSearchResultsPanel.Analyzers.ResultAnalyzer.Analyze(BibleReferenceResourceResults results, LibraryCatalog libraryCatalog, ReadOnlyCollection`1 referenceRange, ResultAnalyzerOptions option, IWorkState state, VersifiedResourceManager vrm)
   at LDLS4.Panels.GraphBibleSearchResultsPanel.ChartGraphBibleVisualization.<UpdateChartModelWork>d__27.MoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.EnumMoveNext()
   at Libronix.Utility.Threading.AsyncWorkerTask`1.ContinueExecution(Object unused)
   at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(Object state)
   at System.Threading.QueueUserWorkItemCallback.WaitCallback_Context(Object state)
   at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
   at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()
   at System.Threading.ThreadPoolWorkQueue.Dispatch()
   at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback()

Thanks,

David

Mike

Hi David,

Yes, that is the crash or "callstack" but it is out of context on its own. When we have it int he Logos.log file, we can get a lot more data about what Logos was attempting to do leading up to it.

David Bailey

Thanks Mike. Lord willing, I will re-index tomorrow.

David

Dave Hooton

Yes, that is the crash or "callstack" but it is out of context on its own. When we have it int he Logos.log file, we can get a lot more data about what Logos was attempting to do leading up to it.

Here you go

3683.GraphResultsCrash.zip

Essentially, run a Morph Search on καθαρισμός in LXX Swete and then press Graph Results to get a crash.

Logos LXX was OK, as are the 2x Lexham LXX Int.

It is reproducible with LXX Swete, and I'm not about to re-index as the issue comes with Graphing.

David Bailey

Steps:

1. Open BWS and enter a greek word (i.e οναι, καθαρισμός, etc) that is also found in the LXX

2. Run the report.

3. Under Textual Searches section, click on LXX to launch the Search - Morph results, using the search parameters shown.

4. Click on "Graph results"

Mike,

I highlighted the item to click in the screenshot above...

thanks,

David