CRASH: Clicking links in Syntax search results

Kevin Becker
Kevin Becker Member Posts: 5,604 ✭✭✭
in Beta Desktop App Forum

I was clicking the links in the syntax search results and Logos crashed.

Logs:

0714.Logos4Crash.txt

6661.Logos4.log

I got the dreaded Document ID out of range message... does this mean I need to rebuild my index [:(]?

Prov. 15:23

How to ask for Help

Comments

  • Dave Hooton
    Dave Hooton MVP Posts: 35,772

    I think you should update to RC1 before jumping to conclusions.

    Dave
    ===

    Windows 11 & Android 13

  • Kevin Becker
    Kevin Becker Member Posts: 5,604 ✭✭✭
    https://community.logos.com/discussion/comment/125644#Comment_125644

    Dave Hooton said:

    I think you should update to RC1 before jumping to conclusions.

    I hadn't jumped to any conclusions...

    Thanks for pointing out the RC... I hadn't noticed it yet. We'll see what happens.

     

    Prov. 15:23

    How to ask for Help

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969

    Kevin Becker said:

    I was clicking the links in the syntax search results and Logos crashed.

    I got the dreaded Document ID out of range message... does this mean I need to rebuild my index Sad?

    The error isn't actually "Document ID out of range" (it's something else out of range). So you don't need to rebuild your index. This is a bug that's been reported before, but which we've never been able to reproduce.

    Can you make it happen again? If so, can you describe the syntax search, and which result you're clicking to reproduce the crash?

  • Dave Hooton
    Dave Hooton MVP Posts: 35,772
    https://community.logos.com/discussion/comment/125665#Comment_125665

    Kevin Becker said:

    Dave Hooton said:

    I think you should update to RC1 before jumping to conclusions.

    I hadn't jumped to any conclusions...

    Thanks for pointing out the RC... I hadn't noticed it yet. We'll see what happens.

    Sorry Kev, I didn't mean to be so abrupt - I wasn't convinced it was a index error and wanted you to at least try it with the RC1.

    Dave
    ===

    Windows 11 & Android 13

  • Kevin Becker
    Kevin Becker Member Posts: 5,604 ✭✭✭
    https://community.logos.com/discussion/comment/125675#Comment_125675

    Bradley Grainger said:

    Kevin Becker said:

    I was clicking the links in the syntax search results and Logos crashed.

    I got the dreaded Document ID out of range message... does this mean I need to rebuild my index Sad?

    The error isn't actually "Document ID out of range" (it's something else out of range). So you don't need to rebuild your index. This is a bug that's been reported before, but which we've never been able to reproduce.

    Can you make it happen again? If so, can you describe the syntax search, and which result you're clicking to reproduce the crash?

    I'm glad I misread the logs then [:)] Here's what happened, I was trying to figure out what made the syntax search engine count a verse multiple times as asked here: http://community.logos.com/forums/t/16563.aspx

    So I ran this syntax search to generate a baseline

    image

    Then I modified the same syntax search document to this (only modifying the Matching skips levels on Segment 1)

    image

    I ran that search, now I had two sets of results. I clicked on Ex 13:9 in the 2nd search result pane, bringing up the A-F Graph over the 1st search result pane. I adjusted the pane to view the result in question a little better. Then I clicked the second result, 2 Kings 10:31 and Logos crashed.

    I was able to reproduce the issue this morning with 4.0c RC 1. Last night with the initial crash I was able to click around in the results more than what I  was this morning so you might have to jump around a bit in the results before a crash.

    Here are the logs from this morning's crash, just in case they have anything else that might be helpful.
    2018.Logos4Crash.txt
    6558.Logos4.log

    Prov. 15:23

    How to ask for Help

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭
    https://community.logos.com/discussion/comment/125745#Comment_125745

    Kevin Becker said:


    I was able to reproduce the issue this morning with 4.0c RC 1. Last night with the initial crash I was able to click around in the results more than what I  was this morning so you might have to jump around a bit in the results before a crash.

    Here are the logs from this morning's crash, just in case they have anything else that might be helpful.

    Thanks, I've added this thread and log file to the open case.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969
    https://community.logos.com/discussion/comment/125745#Comment_125745

    Kevin Becker said:

    I ran that search, now I had two sets of results. I clicked on Ex 13:9 in the 2nd search result pane, bringing up the A-F Graph over the 1st search result pane. I adjusted the pane to view the result in question a little better. Then I clicked the second result, 2 Kings 10:31 and Logos crashed.

    Thanks; I can reproduce the crash by navigating between the two references you cited.

  • Bradley Grainger (Logos)
    Bradley Grainger (Logos) Administrator, Logos Employee Posts: 11,969
    https://community.logos.com/discussion/comment/125858#Comment_125858

    Bradley Grainger said:

    Thanks; I can reproduce the crash by navigating between the two references you cited.

    This will be "fixed" for the next RC. Specifically, the program will not crash when you click the "2 Kings 10:31" link. However (if the previously-displayed reference was Ex 13:9) it will incorrectly jump to 2 Kings 11:1. Clicking the hyperlink again will jump to the right verse.

    We will try to fix the underlying issue (causing the incorrect navigation) in 4.0d.

This discussion has been closed.

Categories