BUG: Crash, caused by duplicated search ranges?

In Logos 5, several of the ranges I've set up for Bible search are duplicated, and when I try to scroll the list, Logos crashes (shut down by Windows).

Is this a new bug? A Synch problem? I did manually set up ranges on my Android phone as well, and the duplicated ones do look like they might be those.

I can choose "All Passages" from the top of the Ranges list, but if I try to scroll down the list of ranges, the program crashes every time. I was able to delete some of the duplicates from near the top of the list, but I can't scroll down to delete the ones further down the list without crashing.

(FWIW, this range-"synching" isn't bidirectional, i.e. the Android app doesn't have all the passage ranges I defined on the PC.)

Logos 5.1.0.0943 on Win 7 SP1 (64-bit)

Bible 2.4.7.2 (Build 108) on Android 4.1.2.

Find more posts tagged with

Comments

Mark Smith

There was an earlier bug that crashed the program in beta testing (it was fixed in 5.1 Beta 6) when you had a named range that had a title but didn't have a scripture range listed after it. Example: Gospels rather than Gospels (Matthew-John). It sounds like you have a similar bug or the same one has cropped up again. I think Logos will need to look into this.

Bradley Grainger (Logos)

when I try to scroll the list, Logos crashes (shut down by Windows).

Please post your "Documents\Logos Log Files\LogosCrash.txt" file (to help us identify the problem).

Allen Browne

https://community.logos.com/discussion/comment/503229#Comment_503229

Please post your "Documents\Logos Log Files\LogosCrash.txt" file (to help us identify the problem).

Thanks, Bradley.

Here are the log files with today's date:

http://allenbrowne.com/temp/AllenBrowne_RangeCrash.zip

Bradley Grainger (Logos)

Is this a new bug? A Synch problem? I did manually set up ranges on my Android phone as well, and the duplicated ones do look like they might be those.

This appears to be a longstanding issue in the desktop app that synching from Android has exposed. (The desktop app expects the reference ranges to be in a certain format, and Android can format them slightly differently.) It's related to the actual content of the ranges; the duplicated titles aren't a problem.

You may be able to work around it by deleting custom reference ranges from Android. Otherwise, we'll have a fix in 5.1 SR-1.

(FWIW, this range-"synching" isn't bidirectional, i.e. the Android app doesn't have all the passage ranges I defined on the PC.)

I'll pass this bug report along to the Android team.

Allen Browne

https://community.logos.com/discussion/comment/503302#Comment_503302

You may be able to work around it by deleting custom reference ranges from Android.

Thanks, Bradley.

Logos 5 is no longer crashing after deleting all my custom reference ranges on the Android phone, so that's solved my immediate problem. Appreciated.

I now have some ranges that I hadn't noticed before, under the heading "COMMON DIVISIONS".

Most of these make sense, except for:
Johannine Epistles (Luke, 1 John - 3 John)

I would like to delete (or modify) that one.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/503320#Comment_503320

I now have some ranges that I hadn't noticed before, under the heading "COMMON DIVISIONS".

Most of these make sense, except for:
Johannine Epistles (Luke, 1 John - 3 John)

I would like to delete (or modify) that one.

These are built-in to Logos 5.1 and can't be deleted or modified. However, the inclusion of Luke in "Johannine Epistles" is clearly an error; we'll fix that.

kelly.flones

https://community.logos.com/discussion/comment/503320#Comment_503320

Most of these make sense, except for:
Johannine Epistles (Luke, 1 John - 3 John)

I would like to delete (or modify) that one.

This reference range no longer includes Luke. This fix will be in 5.1 SR-1.

Allen Browne

https://community.logos.com/discussion/comment/504880#Comment_504880

Johannine Epistles (Luke, 1 John - 3 John)

This reference range no longer includes Luke. This fix will be in 5.1 SR-1.

Beautiful. Thanks Kelly (and team).

Lee

https://community.logos.com/discussion/comment/504927#Comment_504927

Off-topic:

Can't Logos be programmed to scrub all input/ranges and also crash more gracefully?

As for the desktop app, can't Logos program send a crash dump to Logos server (the setting can either be on or off by default)?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/504941#Comment_504941

Can't Logos be programmed to scrub all input/ranges and also crash more gracefully?

We are starting to do this more. In the past, the data that the desktop app loaded was only created by the desktop app, so the code assumed it was in the specific format that it used. Now, that data is also being created by sync (from a mobile app, which is running different code), so we are eliminating those assumptions and making sure the data is interoperable between the different platforms. Sometimes (e.g., the issue discussed in this thread), we don't account for every possibility, and a problem slips through.

As for the desktop app, can't Logos program send a crash dump to Logos server (the setting can either be on or off by default)?

We do collect crash analytics. In this case, we knew about this specific crash a day before this thread was created. It is likely that we would have fixed it even if this thread hadn't been created. That being said, the initial information that Allen posted was extremely helpful in identifying the exact cause of the crash and developing a fix that handled all possible variations. So please do continue to post if you're experiencing problems. Often it helps us solve the problem; it also helps other customers who may have the same issue.

Francis

https://community.logos.com/discussion/comment/504983#Comment_504983

I too found that my ranges had been duplicated (version 5.1.0.0943). I had no problem deleting them (no crash). However, I don't know how this came about. It is a BUG and I wanted to bring it to attention so that whatever caused it can be avoided in future releases. See picture.