Crash when searching in Beta 2
I did a datasheet search for father* in my top bibles and got the following error each and every time I try. This is in Win7 Pro/64. Other searches work OK:
2009-11-29 06:18:33.6029 4 Error OurApp Unhandled exception: 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 LDLS4.DataGrid.SearchAnalysisDataGridProvider.AnalyzeResults(HitsByResourceResults results, ResourceManager resourceManager, RichTextContentExtractor extractor, IWorkState state)
at LDLS4.Panels.SearchPanel.BibleDatasheetResultsViewModel.<SearchWork>d__0.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.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.Threading._ThreadPoolWaitCallback.PerformWaitCallbackInternal(_ThreadPoolWaitCallback tpWaitCallBack)
at System.Threading._ThreadPoolWaitCallback.PerformWaitCallback(Object state)
2009-11-29 06:18:42.0804 1 Info IsWorkingControl Hiding IsWorkingControl (name id 50900362)
2009-11-29 06:18:42.0804 1 Info IsWorkingControl IsWorkingControl.IsAnimating = False (name id 50900362)
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
-
Mark,
I assume this is a Bible search.
You do not need to use the * at the end. Simply make sure "Match all word forms" is ticked in the pane menu at the top left of the search pane. That is the same. I wonder if both are used if it causes this error. Try it.
I just did it without the * in my top and got 7760 hits and have displayed it in the datasheet.
Chris
0 -
Chris Elford said:
You do not need to use the * at the end.
As a temporary workaround, OK. But the wildcard and stemming (Match All..) are not the same eg. the stemming for father does not include fatherless, so there is a discrepancy of 160 results in my Top Bibles. Which also means I didn't reproduce the crash when I used the wildcard! But it is definitely slow taking 9s vs 0.4s, as I've observed before.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Chris Elford said:
You do not need to use the * at the end.
As a temporary workaround, OK. But the wildcard and stemming (Match All..) are not the same eg. the stemming for father does not include fatherless, so there is a discrepancy of 160 results in my Top Bibles. Which also means I didn't reproduce the crash when I used the wildcard! But it is definitely slow taking 9s vs 0.4s, as I've observed before.
Dave,
I guess this means you've pointed this out before. Hope I remember it this time.
Chris
0 -
I tried it with father* and got 7868 results (108 more) and displayed directly in datasheet - took 112 secs. I think the display really slows it down as it has to display all. In a grid or verses it shows 50 or so and then give pages.
Chris
0 -
Chris Elford said:
I guess this means you've pointed this out before. Hope I remember it this time.
I don't think so! Just that stemming is an algorithmic approach to related word forms. The wildcard * is a straight match for anything beginning with "father", but the algorithm says fatherless is not related to "father"! It doesn't think "spend" and "spent" are related, but spen* will return many unrelated words!
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Chris Elford said:
I guess this means you've pointed this out before. Hope I remember it this time.
I don't think so! Just that stemming is an algorithmic approach to related word forms. The wildcard * is a straight match for anything beginning with "father", but the algorithm says fatherless is not related to "father"! It doesn't think "spend" and "spent" are related, but spen* will return many unrelated words!
A Bible search for "father" without the wildcard displayed in the datasheet took 92 seconds - that means those extra 108 took 20 seconds - I'd say the fact it took 92 secs. is related to the preparation for the datasheet because a grid search for "father" took 8 seconds and displayed in no more than 2 secs. and a grid search for "father*" took 11.4. So, it doesn't seem to be the search part that causes the delay.
Chris
0 -
Chris Elford said:
A Bible search for "father" without the wildcard displayed in the datasheet took 92 seconds - that means those extra 108 took 20 seconds
Yes, the datasheet will clearly take longer than other views. My concern is that Logos may foist the same format on Basic Search to answer our requests to display results by Resource. Also, we want them closed initially to see all resources with results.
Dave
===Windows 11 & Android 13
0 -
Dave Hooton said:Chris Elford said:
A Bible search for "father" without the wildcard displayed in the datasheet took 92 seconds - that means those extra 108 took 20 seconds
Yes, the datasheet will clearly take longer than other views. My concern is that Logos may hoist the same format on Basic Search to answer our requests to display results by Resource. Also, we want them closed initially to see all resources with results.
I share your concern.
0 -
Mark Barnes said:
I did a datasheet search for father* in my top bibles and got the following error each and every time I try. This is in Win7 Pro/64. Other searches work OK:
This has been reported.
Thanks,
Melissa0 -
Mark Barnes said:
I did a datasheet search for father* in my top bibles and got the following error each and every time I try. This is in Win7 Pro/64. Other searches work OK:
2009-11-29 06:18:33.6029 4 Error OurApp Unhandled exception: System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values.
This will be fixed after Beta 3.
0
