Highlights crash

Gregory Lawhorn
Gregory Lawhorn Member Posts: 982 ✭✭✭
edited November 2024 in English Forum

This is a predictable crash. 

I have my Bible open.

I have the Highlight panel open. 

I want to save highlights in a Note file. 

I click on the triangle to the right of the name of the Highlight group.

At the bottom of the popup is "Notebook: No notebook" with an expansion triangle.

I move the cursor to "Notebook: No notebook".

Voila! Logos is gone. 

Tagged:

Comments

  • Graham Criddle
    Graham Criddle MVP Posts: 32,756

    Are you running on Mac with Mojave 10.14.0?

    If so, upgrading the OS to 10.14.1 should fix this

  • Gregory Lawhorn
    Gregory Lawhorn Member Posts: 982 ✭✭✭

    Are you running on Mac with Mojave 10.14.0?

    If so, upgrading the OS to 10.14.1 should fix this

    Ah, yes, I was still running the public beta, and the Mac App Store wouldn't automatically update the OS, so I didn't look carefully. I'm all good now! 

    Thanks, Graham

  • Roy
    Roy Member Posts: 965 ✭✭

    Graham, or anyone else who may know...

    I am running my LOGOS install on a MacPro 5.1 with 2 AMD 5770 video cards.
    12 cores
    32 Gig ram
    Tons of hard drive space (4 - 3Tb drives)
    and MacOS El Capitan.

    I can not upgrade to MacOS 10.14 due to the video cards.
    I have already blown the majority of my discretionary cash on the Logos8 upgrade.

    Is there ANY thing I can do short of an OS upgrade to get my Logos install to stop crashing inside of NOTES as mentioned above by the O.P.??

    I can go ahead and upgrade my OS version to High Sierra, I just have not as of yet, "needed" to do so I would have to do so in order to upgrade to MacOS 10.14 anyway..

    ( So far with a cursory web search, it will cost me something like $500 plus (U.S.D)  to get the new vid cards just to go the new OS version, just to "fix" the crashing issue.)

    I can get around this by running Logos in a Windows VM on the Mac but that will cause me to take a huge performance hit.

    My preference is to see the programmers there find a programaic solution instead of saying to just upgrade to the next OS. Not everyone can do that, nor should they have to. There has to be a better solution. 

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

    There were a number of crashes in macOS Mojave 10.14.0 that were fixed in 10.14.1. That is what Graham was recommending.

    If you are not running Mojave, then his advice doesn't apply to you. Please start a new thread with details of your crash, including logs, and we can help you.