BUG: Logos 6.4 SR-2 Text Comparison doesn't render properly in narrow window with 6 or more Bibles and "Show base text" enabled

Page 1 of 1 (9 items)
This post has 8 Replies | 1 Follower

Posts 23
Ian.M | Forum Activity | Posted: Mon, Jul 6 2015 4:54 PM

I'd like to report a bug I have observed in Logos 6 on Windows. 

I'd like to have Logos respond and confirm if they can reproduce the problem and I'd love it if they could confirm they'll work toward a resolution in a future patch of L6.

Also, I'd be interested to know if anyone else has encountered this or can reproduce it. Is anyone aware of another forum thread that addresses this?


Here's my environment:

Windows 8.1 Pro x64 (running on Microsoft Surface Pro 3 hardware)

Logos Bible Software 6.4 SR-2 (build


To reproduce issue:

- Open Logos 6.

- Close all windows.

- Open a "Text Comparison" window in a tall narrow window as in the screenshots below.

- Enter any 6 English Bibles into the list of Bibles to compare and choose a Bible verse that is relatively long (I've observed it on Romans 1:13 today) and then enable the options for both "Show differences" and "Show base text"


Symptoms of the problem:

- In the above scenario the latter parts of the tool's output will not properly display in the narrow Window.  In my case the display alternates as in the screenshots below. It will show some of the text at the bottom of the screen for a few seconds, then more, then less.  Sometimes it entirely omits the output from the 6th Bible version included in the list. Sometimes it sorts itself out after several minutes but often it just continues this loop until either the window is resized, fewer Bible versions are compared, or the "Show base text" feature is disabled.



- This issue only occurs with narrow windows and it has only occurred for me with narrow windows where I'm trying to compare 6 or more Bibles, and the issue only occurs when the Bible verse is relatively long, and it only occurs when "Show base text" is enabled


Suspected Cause:

- I suspect that the issue is that the "Text Compare" code has a bug which doesn't handle the narrow window properly.  The problem seems to be that the code expects the window to be larger when these conditions are configured.



- The problem exists when "Text Comparison" window is tall and narrow.  For comparison I've opened two "Text Comparison" windows. The wide window on the left works fine, but the narrow window on the right demonstrates the problem.  I've drawn a red arrow to point towards where the problem occurs.  The following screenshots show how the bottom lines of the output on the narrow window don't display properly and just alternate between the text shown.  You'll notice that the narrow window on the right never shows the entirety of the 5th Bible's text (the NET in this example), or any of the text from the 6th-9th Bibles.

- In these examples I am attempting to run "Text Compare" against these Bibles: " ESV, NASB95, LEB, HCSB, NET, NIV84, RSV, NKJV, 1901 ASV"

- These are sequential screenshots that show the various steps of the repeating loop:

Thanks all!

Posts 8681

We have a case for this bug in our bug database; I've added a link to this thread to the bug report.

For now we recommend using a wider panel or opening Text Comparison in a floating window as a workaround.

Posts 23
Ian.M | Forum Activity | Replied: Mon, Jul 6 2015 5:04 PM

Thanks for the quick reply Bradley!  Can you share what release of Logos you're targeting for the fix?

Posts 8681

It's not currently scheduled for a specific release. So far, we've had difficulty reproducing the problem. I tried again with your steps but was unsuccessful. What screen resolution do you use, and are you running Logos maximised? Do you have a high-DPI display or Program Scaling set above 100%?

Posts 23
Ian.M | Forum Activity | Replied: Tue, Jul 7 2015 6:46 AM

Thanks again for your response Bradley. That's clever troubleshooting Smile

Yes, the Microsoft Surface Pro 3 tablet that I'm using does have a higher than usual screen resolution and DPI.  However, I've been able to reproduce the issue  on a system with a normal screen.

On my Surface Pro 3, the default resolution is 2160 x 1440 (see also https://www.microsoft.com/surface/en-us/products/surface-pro-3 ), and that's what I'm running:



Also, I have the default DPI scaling. It's my understanding that this value represents 150% scaling (and again this is the default):


Lastly, I am executing "C:\Users\Ian\AppData\Local\Logos\Logos.exe" with Window's default compatibility options.  (This is Window's 8.1 "Compatibility" tab for the Logos.exe file properties window.  Notice that "Disable display scaling on high DPI settings" is not enabled.)


Yes, I am running Logos.exe as a fully-maximized Window on my desktop. The behavior also occurs on a non-maximized Logos.exe.


However, as I mentioned above, today I've also been able to reproduce the issue on a system that doesn't have a high resolution and has 100% DPI scaling, so it seems like the issue may not be caused by the monitor/video settings.

Below is a video I made of the issue that I was able to reproduce on a Windows Server 2008 R2 Enterprise x64 machine running Logos 6.4 SR-2 ( with 1440 x 1050 resolution and 100% DPI in a fully-maximized Logos.exe window.  I'm accessing this Win2008 server via RDP and the machine is a virtual machine hosted within Vmware ESXi, but I don't think that should affect this troubleshooting. 

3007.Logos 6 Text Comparison Bug demo video.mp4


Posts 8681

Thanks for the video. I was able to reproduce and I think we can get a fix in 6.5.

Posts 23
Ian.M | Forum Activity | Replied: Tue, Jul 7 2015 12:18 PM

Great! Thanks! I'm looking forward to it. Thanks for your prompt responses Smile

Posts 1471
Angela Murashov | Forum Activity | Replied: Mon, Aug 10 2015 10:47 AM

Bradley Grainger (Faithlife):

Thanks for the video. I was able to reproduce and I think we can get a fix in 6.5.

6.5 is now available on the stable channel and it includes this fix. 

Posts 23
Ian.M | Forum Activity | Replied: Tue, Aug 11 2015 7:00 AM

Thanks for the update Angela. I've updated to and the issue appears resolved. Thanks all!

Page 1 of 1 (9 items) | RSS