repeated crashes

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

Im running OS X 10.14.6 on an iMac with an i7 & 24GB ram with Logos 8.8.0.0046. I use a multi monitor lay out with panes spread across 3 different screens. 

0317.LogosLogs.a3w275.20191024-121624.zip

I have crashed L8 5-6 times already this morning, just entering in the reference Rom 14 into an NASB Bible, or clicking on a link to romans in a search panel. 

I have already: restarted the computer. I have reindexed my library. I have completely and manually rebuilt my layout from a blank lay out to the one I use for working. Still it crashes.

Here are my log files. can anybody tell me what is going wrong and give suggestions? This is bad enough right now it is getting really difficult to accomplish anything. 

Tagged:

Comments

  • MJ. Smith
    MJ. Smith MVP Posts: 53,830

    Sorry I don't do Mac but the error appears to be:

    System.Net.WebException: Error: SecureChannelFailure (Unable to write data to the transport connection: The socket is not connected.) ---> System.IO.IOException: Unable to write data to the transport connection: The socket is not connected. ---> System.Net.Sockets.SocketException: The socket is not connected
    at System.Net.Sockets.Socket.EndSend (System.IAsyncResult asyncResult) [0x00012] in <8a5c82c9d175415698df08ed5961ac11>:0

    Orthodox Bishop Alfeyev: "To be a theologian means to have experience of a personal encounter with God through prayer and worship."; Orthodox proverb: "We know where the Church is, we do not know where it is not."

  • Dave Hooton
    Dave Hooton MVP Posts: 35,868

    Tim said:

    I have crashed L8 5-6 times already this morning, just entering in the reference Rom 14 into an NASB Bible, or clicking on a link to romans in a search panel. 

    Does it only happen under those circumstances?

    Please capture the logs after entering Ro 14 in NASB (and crashing). But upload the logs before you restart Logos.

    Dave
    ===

    Windows 11 & Android 13

  • Tim
    Tim Member Posts: 256 ✭✭
    https://community.logos.com/discussion/comment/1072674#Comment_1072674

    Thanks for the responses. I ended up calling support and 3 hours later the person I spoke with confirmed that I had managed to put together a layout that when crossed with a formatting/code problem in the NASB causes a crash.

Categories