CRASH: Passage Analysis / Version River

Chris Heil

Choosing the Version River option within the Passage Analysis for Luke 1:1-13 using a previously-created Collection called "Top English Bibles" which includes 29 Bibles (see below) is causing a crash within 1 to 5 seconds of display.  Log files are attached. I am on Logos Max (early) 35.0.520 on a Windows 11 PC.

Logos.zip

 

Dave Hooton

I can reproduce with a larger collection of 41 bibles. It did not crash with 5 Top bibles.

Matt Mattox

Chris Heil said:

which includes 29 Bibles (see below) is causing a crash within 1 to 5 seconds of display

Thank you for the report. I was able to replicate the issue when using a collection of about 12 or more Bibles while also hovering over the river. You mentioned a display time of 1-5 seconds—by any chance, were you also hovering over the river during that time of the crash?

Chris Heil

https://community.logos.com/discussion/comment/1310031#Comment_1310031

Matt Mattox (Faithlife) said:

Thank you for the report. I was able to replicate the issue when using a collection of about 12 or more Bibles while also hovering over the river. You mentioned a display time of 1-5 seconds—by any chance, were you also hovering over the river during that time of the crash?

Good catch on the hover.  I don't think you have to hover per se, but as long as the mouse passes over the river, the app will crash a second or two later.  I was trying to click different elements on the screen so the timeframe was dependent upon when my mouse passed over it to cause the 1-5 second delay.

There is a joke in here somewhere about the river parting...

Matt Mattox

https://community.logos.com/discussion/comment/1310044#Comment_1310044

Thanks for the information. The fix is currently implemented in our v36 beta application and therefore will soon be available in an upcoming stable release (v36) in the Logos Desktop application. 

Chris Heil

https://community.logos.com/discussion/comment/1310066#Comment_1310066

Matt Mattox (Faithlife) said:

Thanks for the information. The fix is currently implemented in our v36 beta application and therefore will soon be available in an upcoming stable release (v36) in the Logos Desktop application. 

Thank you Matt!