BUG: Greek NT crashes at 3Jn

Tim
Tim Member Posts: 256 ✭✭
edited November 21 in English Forum

After numerous crashes I was able to narrow down that this resource will cause a crash at 3Jn. Tested across multiple (Mac) computers so it doesn't seem to simply be a corrupt resource on a single computer. 

LLS:1.0.337
2007-01-04T22:51:10Z
GNTMAJ.lbxlls

Tagged:

Comments

  • Graham Criddle
    Graham Criddle MVP Posts: 32,634

    Hi Tim

    Tim said:

    After numerous crashes I was able to narrow down that this resource will cause a crash at 3Jn. Tested across multiple (Mac) computers so it doesn't seem to simply be a corrupt resource on a single computer.

    I've just tried with that resource on my MacBook and it acccesses 3 John just fine!

    I recommend enabling logging and uploading log files in a reply to this thread after a crash

    Details at https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files 

    Graham

  • DMB
    DMB Member Posts: 3,087

    Wow, that must be a serious bug.  Closes out 5 windows and 110 resources in a microsecond!  Mac, Ventura; latest Verbum 24.x.

    EDIT: I just saw Graham's no-problem post.  So I tried various combinations of addressing 3 John ... consistent crashes.

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 916

    Tim said:

    After numerous crashes I was able to narrow down that this resource will cause a crash at 3Jn.

    I can take a look today and see if I can replicate this issue. 

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 916

    I'm not able to replicate when scrolling to Jn 3 when on my mac using version 24.0.14

    Your logs will help from the link posted above if you can upload your log files. Otherwise, any other information you have that can help us track it will be helpful too. Let me know if I am doing anything wrong when opening that resource and going to John 3

  • DMB
    DMB Member Posts: 3,087

    Hi Matt 

    Again thank you for the followup.  I'm barely operable on a Mac, so no logs.  However, I did see why the crash occurs (using it).  If you turn on the Bible Text Only visual filter, and then turn each sub-filter on one by one, it'll crash on the last one (One verse per line.)  

    At least my testing.  I also tried scrolling into 3 John, and still, it gets a whiff of 3 John and gone (if One verse per line is checked).

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 916

    DMB said:

    If you turn on the Bible Text Only visual filter, and then turn each sub-filter on one by one, it'll crash on the last one (One verse per line.)

    Ah, that was it. Well done, that was very helpful. I'll write up a case. Again, nice work :) 

  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 916

    Are you still crashing? I'm no longer able to replicate this again and curious if you are still experiencing the issue?

  • DMB
    DMB Member Posts: 3,087

    Are you still crashing? I'm no longer able to replicate this again and curious if you are still experiencing the issue?

    Yes.  A one-line-only filter setting is an instant crash; removing the checkmark achieves nirvana.  I tried the content% setting issue from the morning's 'research' ... that doesn't seem to impact the 3John crash any.

    I'm also impressed, that if you're 'in' 3John (one-line-only filter unchecked), and then just change the filter, the app is gone.  In other words, not a book/chapter milestone crossover issue (guessing).

  • Ali Pope
    Ali Pope Member, Logos Employee Posts: 1,821

    Matt and I are still unable to reproduce this issue. Logs would be most helpful in this situation (instructions here).

    DMB, I know Mac logs may not be an option for you, so in its absence, any of the following would be helpful:

    1. Could you send a screenshot of your Program Settings and/or your visual filter settings?
    2. Could you send a screen recording of the crash?

    Thanks in advance for any additional information you can provide Matt and I, as we continue to nail this crash down!

    Ali Pope | Logos Desktop and Mobile Program Manager

  • DMB
    DMB Member Posts: 3,087

    Ali Pope said:

    • Could you send a screenshot of your Program Settings and/or your visual filter settings?
    • Could you send a screen recording of the crash?

    I don't know screen recordings; but click on One-Line in VFs and poof. I do notice that if the book title is displayed (below 2 John text), but no verses, it's happy.  But just touching the scroll and poof.  Any hint of verse-line display and it's gone.

    Here's the settings and VFs:

  • Graham Criddle
    Graham Criddle MVP Posts: 32,634

    Hi Ali

    Ali Pope said:

    Matt and I are still unable to reproduce this issue. Logs would be most helpful in this situation

    I managed to recreate the problem following DMB's outline 

    I had these visual filter settings before enabling the one verse per line option which cause Logos to crash immediately.

    Logs below

    5488.LogosLogs.grahamcriddle.20230404-190338.zip

    Hope this helps, Graham

  • Beloved Amodeo
    Beloved Amodeo Member Posts: 4,181 ✭✭✭

    Meanwhile, Jesus kept on growing wiser and more mature, and in favor with God and his fellow man.

    International Standard Version. (2011). (Lk 2:52). Yorba Linda, CA: ISV Foundation.

    MacBook Pro MacOS Sequoia 15.2 1TB SSD

  • Tim
    Tim Member Posts: 256 ✭✭
    Sorry its taken me a bit to reply back to this thread. Yes, this is still happening and I'm thankful to DMB for further narrowing down the behavior to the one verse per line filter which is indeed what I use for all my study. I've attached my own logs here as well. I started with a blank lay out, opened the book in question, turned OFF the filters, scrolled to 3Jn and then back to 1Jn, turned ON only that filter and then scrolled back to 3Jn and the application crashed with only that resource and that single filter enabled.
  • Matt Mattox
    Matt Mattox Member, Community Manager, Logos Employee Posts: 916

    Thanks, someone from our team was also able to replicate. With their log files and the log files attached to this forum thread. We should have enough information to track down the root of the issue. 

  • Tim
    Tim Member Posts: 256 ✭✭