4.5a beta 1: Crash in Bible Search on PB
I'm getting a crash when doing a Grid Search on a Personal Book Bible. It doesn't seem to matter what word I search for. The other searches seem to work fine.
Error ID: 6350
Error detail: InvalidOperationException: Operation is not valid due to the current state of the object.
As well as Error ID 6350 in the crash log, I've also had Error ID 8531 in the error log.
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
-
I haven't been able to reproduce this with the sample PB Bible that I have. Can you give a URL to the source of this PB Bible, or email the source docx to logos4feedback@logos.com (please reference this thread) so we can try to reproduce the crash?
0 -
Hello Bradley. Thanks for giving us back the function of the Bible search in PB Bibles. I can confirm that it works. I built a new Test Bible (just Genesis) and it works great.
I got some crashes however when trying to do a Bible search of the Top Bibles and 1 of them is the previously built PB Bible (not the newly built Test Bible). It crashed my Logos 4 session.
Here are my logs: 8662.Logos4LogsBWojnar.zip
Bohuslav
0 -
I haven't been able to reproduce this with the sample PB Bible that I have. Can you give a URL to the source of this PB Bible, or email the source docx to logos4feedback@logos.com (please reference this thread) so we can try to reproduce the crash?
It was using my Tyndale Bible: http://community.logos.com/forums/t/37523.aspx
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,
There were also some Sync errors in your log files. I've made some fixes to server code that should have cleared those up.
Does everything seem to syncing now (ie no yellow triangle in the upper right)?
0 -
I'm getting a crash when doing a Grid Search on a Personal Book Bible. It doesn't seem to matter what word I search for.
I'm not able to reproduce this, no matter what word I search for (including very common terms such as "God" or "the"). I built the Tyndale Bible with the latest document that was posted on the forums.
What are some search terms that are crashing for you? Can you verify that your Logos4\Data\RANDOM\PersonalBookIndex files are newer than the last time you built the Tyndale Bible (in the Personal Books panel)?
0 -
I still get the crash after trying to search the PB Bibles. I recompiled one to see if that would help but no, Logos crashes in the moment I hit search with a common word like "Adam".
I included logs in the previous post.
P.S. My test Bible with just Genesis Bible book works fine. Any other PB Bibles I tried crash Logos.
Bohuslav
0 -
What are some search terms that are crashing for you?
Every word I've tried causes the crash (God, erth), and so on.
Can you verify that your Logos4\Data\RANDOM\PersonalBookIndex files are newer than the last time you built the Tyndale Bible (in the Personal Books panel)?
The index files are dated 26 Jan 2012. 22:20 for LibraryIndex.db, 01:28 for all the other files. The Bible itself was built on 29 August 2011 using Logos 4.3.
I noticed when doing an Aligned", Verses or Analysis search, it says it's found the results in two resources. Could that be a cause?
Doing some digging, I only have one entry for the Tyndale Bible in my Personal Book pane (and in PersonalBookManager.db). Likewise I only have one entry in my library (and in catalog.db). Clicking either search result takes me to the same resource. Unless there's another bug, but it seems as though the file as been indexed twice, and that's now confusing the grid search.
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 -
it says it's found the results in two resources. Could that be a cause?
I think you nailed it Mark. [Y]
Bohuslav
0 -
I noticed when doing an Aligned", Verses or Analysis search, it says it's found the results in two resources. Could that be a cause?
That seems likely. Please email your Logos4\Data\RANDOM\PersonalBookIndex\LibraryIndex.db file to logos4feedback@logos.com (and reference this thread); this should help us understand how the problem happened.
0 -
The file is attached. To my eye, everything looks OK (I already checked for duplicates in that database). My Tyndale Bible has the ResourceId of PBB:6f22819a63f74ae5b6f9b55ccf2c8455. If you want me to send the other files in that folder, I can put them on DropBox or something.
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 -
Interestingly enough, I just found that my Test Bible (just Genesis, named in Czech "Bible Pokus") that is not crashing Logos in the Grid Search do not has the 2 resources information we see in other PB Bibles (that crash Logos).
Bohuslav
0 -
To my eye, everything looks OK (I already checked for duplicates in that database). My Tyndale Bible has the ResourceId of PBB:6f22819a63f74ae5b6f9b55ccf2c8455.
Does that resource ID also appear in the IndexedResources table in your BibleIndex\LibraryIndex.db?
I suspect that it was indexed in the BibleIndex (when you built it in 4.3) and now in the PersonalBookIndex (with 4.5a). When we search and merge results from both indexes, we get two results for the same resource (which is unexpected, and causing the crash).
If this is the case, running "rebuild bible index" should fix it. (I haven't decided if there's an easy way for us to fix this; we might just decide to make 4.5a Beta 3 automatically rebuild the Bible Index if it contains any PB Bibles.)
0 -
Does that resource ID also appear in the IndexedResources table in your BibleIndex\LibraryIndex.db?
Yes, it does. It was also listed in the Resources table with a status of 3 (which I think means 'indexed', doesn't it?).
If this is the case, running "rebuild bible index" should fix it.
I ran Rebuild Bible Index, but according to the log and LibraryIndex.db, all the PBBs got added back in. The two files are attached.
we might just decide to make 4.5a Beta 3 automatically rebuild the Bible Index if it contains any PB Bibles
You probably need to do that anyway. Perseus is being included in the index, too.
If this is the case, running "rebuild bible index" should fix it
It didn't (not surprisingly, given the above).
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 -
I ran Rebuild Bible Index, but according to the log and LibraryIndex.db, all the PBBs got added back in. The two files are attached.
Thanks for testing this out. I haven't reviewed the code thoroughly yet, but I think the determination of whether a resource should be indexed or not is cached (for speed). Thus, the BibleIndex thinks that it should include your PBs (based on that cached value), even though it shouldn't.
Deleting the entire BibleIndex folder should fix this problem (but will take longer because the LibraryIndex.db will need to be completely rebuilt).
Thanks very much for letting us know that we can't just force a "rebuild index" to fix the problem; we'll have to have a more sophisticated solution.
0 -
Deleting the entire BibleIndex folder should fix this problem (but will take longer because the LibraryIndex.db will need to be completely rebuilt).
Deleting the Bible Index folder did the trick. Now it shows just one resource in the Grid results of the Bible search and Logos doesn't crash. Good job Bradley. [Y]
Bohuslav
0 -
This is reported as fixed in 4.5a beta 3.
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
