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.
Comments
-
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.
0 -
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
0 -
-
Thanks Mike. Lord willing, I will re-index tomorrow.
David
0 -
Mike (Tech Support) said:
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
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.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:
It is reproducible with LXX Swete, and I'm not about to re-index as the issue comes with Graphing.
I agree. Thanks, Dave, for checking this issue from my original post.
0 -
I'm hoping we will hear from Logos quite soon.
Dave
===Windows 11 & Android 13
0 -
Sorry guys,
What am I doing differently, here? I still can't get it to crash. Searched lemma:καθαρισμός, in LXX Swete, using Verses view, clicked "Graph Results". All graphs show and do not cause a crash. 5.0b SR-3.
[EDIT: Have you applied any custom tags to LXX Swete? Do you also have a sync error?]
0 -
David Bailey said:
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
0 -
Mike (Tech Support) said:
I still can't get it to crash.
I just tried my steps above and no longer get a crash. However, when I click on "Show zero items" the program crashes.
Attached logs: 6874.LogosCrash.zip
thanks,
David
0 -
-
Mike (Tech Support) said:
And you guys haven't applied any custom tags to LXX Swete? What version of the book do you have installed?
I do not have custom tag for LXX Swete. My version is:
LLS:OTGRKSWETETXT
2012-11-14T18:53:21Z
OTGRKSWETETXT.logos4Mike (Tech Support) said:I still get results:
Try the Column Chart and Bar Chart.
David
0 -
All charts work for me. Same version of the resource.
I just rebuilt my index over the weekend. I still suspect this could be index-related. It is displaying search results, and search results are generated from the index, but I'll see if I can get some input from one of our developers.0 -
Mike (Tech Support) said:
All charts work for me. Same version of the resource.
I just rebuilt my index over the weekend. I still suspect this could be index-related. It is displaying search results, and search results are generated from the index, but I'll see if I can get some input from one of our developers.I can get the Result Map OK (provided a previous Graph is showing Result Map). As soon as I click Column Chart Logos crashes.
I also have the same version of Swete, but don't plan on re-indexing for this resource.
Dave
===Windows 11 & Android 13
0 -
Hey guys,
Thanks for your patience. I was able to reproduce. It looks like the "Show Zero Items" function is causing the crash in both of your cases. This setting is also remembered, so it automatically crashes if we run that graph again. We'll get this worked out ASAP.
Do you have a saved layout with the Results Graph open to a different graph style? This may allow you to work-around the crash by avoiding that setting.
0 -
Mike (Tech Support) said:
Do you have a saved layout with the Results Graph open to a different graph style? This may allow you to work-around the crash by avoiding that setting.
Thanks Mike - it's simple enough to generate a Graph from another resource and then run Swete, which adopts those settings i.e. (not showing Zero results.
Dave
===Windows 11 & Android 13
0 -
Hey guys,
Development found the problem. That graph was looking for all datatypes, but assuming they were bible (canon) references. It is possible in some resources that the datatype might be a non-canonical reference. This caused invalid data.
They've fixed it for 5.1, but we're going to try to sneak it into a service release before then if possible.
Thanks for your patience.
0 -
Mike (Tech Support) said:
They've fixed it for 5.1, but we're going to try to sneak it into a service release before then if possible.
Thanks for that (not fixed in 5.1 beta 7, so it must be the next beta!).
Dave
===Windows 11 & Android 13
0 -
Mike (Tech Support) said:
They've fixed it for 5.1, but we're going to try to sneak it into a service release before then if possible.
Thanks, Logo, for the fix in 5.0b SR-4. Thank you, Mike, for getting this bug to development for the fix.
David
0 -
Thanks Mike. It is fixed in Beta 8.
Dave
===Windows 11 & Android 13
0
