CRASH: Text comparison when viewing Ps 13:6 in LEB

Richard Lyall · 2013-09-15T17:29:05+00:00

Using 5.1a SR-1 (5.1.1.0600) * Was viewing Ps 13:6 in NIV84 * Hit F7, to show text in top 5 Bibles, but LEB (#5 top Bible) was replaced with NRSV (#6 top Bible) * Clicked through to main Text Comparison, and only Bibles #1, #2, #3 and #4 show - LEB translation does not show. * Opened LEB to Ps 13:6 in another window, and…

Richard Lyall

Using 5.1a SR-1 (5.1.1.0600)

Was viewing Ps 13:6 in NIV84
Hit F7, to show text in top 5 Bibles, but LEB (#5 top Bible) was replaced with NRSV (#6 top Bible)
Clicked through to main Text Comparison, and only Bibles #1, #2, #3 and #4 show - LEB translation does not show.
Opened LEB to Ps 13:6 in another window, and hit F7.
Logos hangs and has to be force quit.

This happened again after a restart. Happened again with Ps 13:5 in Step 4.

UPDATE: Simpler steps to reproduce:

1. Open LEB to Ps 13:6
2. Hit F7
3. L5 hangs.

2620.Logos.log

Find more posts tagged with

Comments

Dave Hooton

I can reproduce Logos 5.1a "not responding" and crashing when I try to close it. But it works as expected in 5.1b beta! I'm not sure when that will be released but Logos may fix it in a Service Release for 5.1a. We should know soon.

Dave Hooton

https://community.logos.com/discussion/comment/526558#Comment_526558

bump

Bradley Grainger (Logos)

~~This bug will be fixed in 5.1b.~~

I can't reproduce this in 5.1a. (So it may or may not be fixed in 5.1b.) What are your top 6 prioritised Bibles?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/527106#Comment_527106

I can't reproduce this in 5.1a.

I believe this bug was already fixed in 5.1a SR-2. Can you reproduce it with the latest update?

Richard Lyall

https://community.logos.com/discussion/comment/527153#Comment_527153

Seems ok now in 5.1b B1.

Thanks
Richard

Dave Hooton

https://community.logos.com/discussion/comment/527153#Comment_527153

I believe this bug was already fixed in 5.1a SR-2. Can you reproduce it with the latest update?

It is now fixed in 5.1a SR-2 as well as 5.1b beta.