Beta 8 crashes *every time* now (or "More custom highlighting woes")


When beta 7 was released I created a custom highlighting style, upon which L4 crashed (and would repeatedly crash each time I displayed the Highlighting tools panel).  For a while now my only recourse was to hold down Ctrl and load an empty layout (and be careful not to display the Highlighting tools panel).

This morning I upgraded to Beta 8 and found that I would display the Highlighting tools panel - and even see my previously created custom style.  In my eagerness I applied my new style to a single word to test it out. Whereupon L4 b8 crashed.  And now keeps crashing each time I display that passage, regardless of whether or not the Highlighting tools panel is visible. That is, holding down Ctrl and opening an empty layout, and then browsing to the same passage of scripture kills L4. 

So, instead of having to ensure that I don't (accidentally) display the Highlighting tools panel, now I have to ensure that I keep all highlighting turned off and/or don't (accidentally) read Jeremiah 8:1 (where I applied the deadly highlighting).

Logs are attached.

Any chance a patch can be provided for this before the next beta release?

1212.Logos Log Files - beta 8 - highlighting crash.zip

 

Comments

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭

    Stuart, it sounds like you are able to view Jeremiah 8:1 when highlighting is turned off. What if you try this, to remove the "deadly highlighting":

    Turn off highlighting visual filter.

    Select the verse that was highlighted (or a chunk of text that includes all of where you know the highlighting was).

    Click Erase on the Highlighting tool.

    Now see if you can turn highlighting back on without it crashing.

    Even if you can, it sounds like there's still a bug in there that Logos should look into, but at least this might make it so you can work again around that verse. If it works, that is.

  • Dave Hooton
    Dave Hooton MVP Posts: 36,339

    Any chance a patch can be provided for this before the next beta release?

    Try renaming L:\p\Logos4\Documents\mpgkukwo.emv\VisualMarkup\visualmarkup.db

    Dave
    ===

    Windows 11 & Android 13

  • Stuart Robertson
    Stuart Robertson Member Posts: 525 ✭✭

    Hi Rosie,

    I followed your advice - opened an empty layout, browsed to a passage other than Jer 8:1, then turned off Highlighting, browsed to Jer 8:1, selected the passage and clicked "Erase" on the highlighting tool panel.  Then turned highlighting back on - and I'm back in business. :-)

    Thanks for the suggestion.

  • Stuart Robertson
    Stuart Robertson Member Posts: 525 ✭✭

    Hi Dave,

    As my last post indicates I managed to "work around" this issue (following Rosie's advice).  But I'll keep this one in my back pocket for just in case.  Thanks for the assistance.

     

  • Rosie Perera
    Rosie Perera Member Posts: 26,194 ✭✭✭✭✭


    Hi Rosie,

    I followed your advice - opened an empty layout, browsed to a passage other than Jer 8:1, then turned off Highlighting, browsed to Jer 8:1, selected the passage and clicked "Erase" on the highlighting tool panel.  Then turned highlighting back on - and I'm back in business. :-)

    Thanks for the suggestion.


    Great! I'm glad it worked. It was a stab in the dark. I couldn't try it out for you first, because I didn't have the crashing behavior.

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭


    Logs are attached.

     Any chance a patch can be provided for this before the next beta release?

    Stuart,

    I'm glad Rosie's fix worked. I'll submit your log to development. 

    Thanks,
    Melissa

  • Melissa Snyder
    Melissa Snyder Member Posts: 4,702 ✭✭✭
This discussion has been closed.