CRASH: Running syntax search
Description
Crash on running syntax search
Repro
- Open Logos 4
- Click on Search --> Syntax
- Select any Syntax Search
Actual Result
Logos 4 terminates abnormally.
Expected Result
Syntax search results
System Specs
WinXP, Intel Dual Core, 4GB
Comments
-
Thanks, filing a case.
0 -
George Allakhverdyan said:
Thanks, filing a case.
Good... I can't run any syntax searches now with out crashing. [:'(]
0 -
Can anyone repro this issue?
0 -
Hey George, I'm now at the place where I can't run any Syntax searches without crashing. I'm on Beta 2, I have redownloaded the Syntax search database resources, renamed the Syntax searches folder, unselected "use internet" option... any other recommendations for getting Syntax searches to work again?
0 -
TimBahula said:
Hey George, I'm now at the place where I can't run any Syntax searches without crashing. I'm on Beta 2, I have redownloaded the Syntax search database resources, renamed the Syntax searches folder, unselected "use internet" option... any other recommendations for getting Syntax searches to work again?
Right now this is a known issue, we will try to get it fixed for Beta 3. Thanks.
0 -
George Allakhverdyan said:
Right now this is a known issue, we will try to get it fixed for Beta 3. Thanks.
imPatiently waiting!
0 -
I'm having a tough time duplicating this internally. The crash appears to occur when loading the parallel resource(s) for the side-by-side view in the results, and as such may be specific to certain resources.
I've got a couple of questions that may help me get to the bottom of this:
1) Does this still occur in Beta 3. There were a few tweaks that may have affected this for the better.
2) Have you prioritized any resources in your Library Catalog? If so, a list of the top 10 resources may point me in the right direction.
3) Do you have the same issue with the "Verses" view in Bible Search?Director of Engineering for Enterprise and Operations
0 -
Cameron Watters said:
I'm having a tough time duplicating this internally. The crash appears to occur when loading the parallel resource(s) for the side-by-side view in the results, and as such may be specific to certain resources.
I've got a couple of questions that may help me get to the bottom of this:
1) Does this still occur in Beta 3. There were a few tweaks that may have affected this for the better.Yes, still happening in Beta 3. Let me know if you want more logs.
Cameron Watters said:2) Have you prioritized any resources in your Library Catalog? If so, a list of the top 10 resources may point me in the right direction.
I didn't think that I had, but now see that I have ESV, HCSB and Darby in "Prefer these resources"
Cameron Watters said:3) Do you have the same issue with the "Verses" view in Bible Search?
Don't think I had tried that before today. When I just tried, Logos crashed. Logs attached.
0 -
TimBahula said:Cameron Watters said:
3) Do you have the same issue with the "Verses" view in Bible Search?
Don't think I had tried that before today. When I just tried, Logos crashed. Logs attached.
Hope you get this fixed soon, now I can't do any Bible searches as I can't switch off of "Verses" view.
0 -
TimBahula said:
Hope you get this fixed soon, now I can't do any Bible searches as I can't switch off of "Verses" view.
And then I discovered that the view isn't sticky. If I'm really fast I can click on another view and the program won't crash, but everytime I do a right-click Bible search or a Morph search I need to click on another view again.
0 -
So, the crash occurs while it is attempting access whatever resource you have specified as the parallel resource for that view.TimBahula said:
And then I discovered that the view isn't sticky. If I'm really fast I can click on another view and the program won't crash, but everytime I do a right-click Bible search or a Morph search I need to click on another view again.
Any chance you know what that is? It's name is (hopefully) in the little box just above the results view selector. I was hoping it was one of your top bibles (which would've used your prioritized resources), but I can't replicate with any of the resources you listed, so maybe it's something else?Director of Engineering for Enterprise and Operations
0 -
Cameron,
I should have probably split this off into another thread. There are 3 issues:
1) Anytime I perform a Syntax Search, beta 3 (and beta 2 and 1 before that) crashes.
2) Whenever Search results are displayed in Verse view, beta 3 crashes. See attached logs and this screen shot.
3) The view for Search results for searches initiated from a right-click Bible or Morph search defaults to Verse view. So because of issue 2, unless I am quick to click Aligned view, beta 3 crashes. It seems to me that the program should remember my previous Search results view.
0 -
Tim,TimBahula said:2) Whenever Search results are displayed in Verse view, beta 3 crashes. See attached logs and this screen shot.
I notice in the screenshot that you provided that the selection box just below the result view picker contains the text "All". As far as I can tell, we don't have a built-in collection called simply "All". Is that a collection that you created?
If so, you may be able to stop the crash by removing the collection.
Also, if that is a custom collection and it doesn't actually contain all of your resources (as the name would imply) it would be great to get the selection criteria you used to create the collection to help me narrow down which resource we're choking on.
Thanks,
CameronDirector of Engineering for Enterprise and Operations
0 -
I've made a couple changes in Beta 4 to try to address this issue. Once Beta 4 is released, please re-run a bible and/or syntax search and upload the log file whether the app crashes or not. Even if it doesn't crash, the logs should include mention of the resource that is causing the problem.
Director of Engineering for Enterprise and Operations
0 -
Cameron Watters said:
I've made a couple changes in Beta 4 to try to address this issue. Once Beta 4 is released, please re-run a bible and/or syntax search and upload the log file whether the app crashes or not. Even if it doesn't crash, the logs should include mention of the resource that is causing the problem.
Whatever you did fixed the problem with my searches. Yes, I did create a custom collection called All, but I didn't put it in the Search results view. It appeared there automatically.
Do you still want log files?
0 -
Tim Bahula said:
Do you still want log files?
Yes, please. Your log should include information about the resource that was previously crashing the app.
Director of Engineering for Enterprise and Operations
0 -
Cameron Watters said:Tim Bahula said:
Do you still want log files?
Yes, please. Your log should include information about the resource that was previously crashing the app.
As requested, just after running a syntax search.
0
