L5 crashes at startup almost more often than it successfully launches

Hi, I'm wondering if anyone can help, as I've found L5 crashing at startup about as often, sometimes much more often, like about three or four times in a row this morning, before a launch was successful, and again this evening a few times similarly.

I've tried not to click on or close any pane, or try to do anything while there are aspects to the program still launching (e.g. highlighting seems to be one of the last things to show up), as that often seems to correlate with crashes. Also, I've increased by free space on the 128GB SSD today to between 21-26GB free out of 119GB (it varies depending on system restore etc.). But that doesn't seem to have helped much.

I'm not sure what to do next, as this has been happening more frequently recently (75% of the time today, although it's normally only about 20% of the time). I've enabled permanent logging, and attached the log files. Any thoughts?

0044.LogosCrash.zip

Find more posts tagged with

Comments

JT (alabama24)

Any thoughts?

The issue will require someone with more techie credentials than me. [:S]
It would be most helpful if you grabbed the logs immediately after a crash, and before you start Logos again. The time stamp on your logos.log file is 20 minutes after the crash log... which means that they came from a different session.
I used to advise that users not fill up more than half their HD capacity... I am not sure if that same recommendation is warranted with an SSD... however... you still have less than 25% of your capacity free, and the crash log mentions an "out of memory" warning. I don't know if the two are related or not... (I don't think so).

Bradley Grainger (Logos)

The crashes seems to always be coming from the HistoryManager component, so I have two suggestions.

1. Don't open the History panel. This should avoid the code path that is leading to the crash. Hold down the CTRL key at startup to show the Sign In dialog, then check the "Use blank layout" checkbox before clicking Sign In. You will also need to avoid loading layouts that include the History panel.

2. Delete the history database. This will lose all your local history. This file can be found at "C:\Users\John\AppData\Local\Logos4\Data\aytx5cbw.n5q\HistoryManager\history.db".

If it's still crashing after doing one or both of these, please post more logs.

John Duffy

https://community.logos.com/discussion/comment/513161#Comment_513161

Any thoughts?

The issue will require someone with more techie credentials than me.

It would be most helpful if you grabbed the logs immediately after a crash, and before you start Logos again. The time stamp on your logos.log file is 20 minutes after the crash log... which means that they came from a different session.

I used to advise that users not fill up more than half their HD capacity... I am not sure if that same recommendation is warranted with an SSD... however... you still have less than 25% of your capacity free, and the crash log mentions an "out of memory" warning. I don't know if the two are related or not... (I don't think so).

Thanks for your comments in any case [:)]
Actually, the log file is stamped 12 hours and 20 minutes before the crash logs. I had used the Ctrl key when starting L5 in the morning, but not since then, as I had followed the instructions to make error logging permament, which did not work in Firefox, but seemed to do so in IE, but clearly didn't: http://wiki.logos.com/Diagnostic_Logging. I've since tried it just there now by following the instructions to download it and run it, which gave a positive window verifying that logging was enabled, so that should work for next time: http://www.logos.com/support/logos5/windows/problem
I would be surprised if L5 crashed because I had only 20-25GB free for it to play with! There was more free space than this on initial installation with L5 and other programs, but I've recently reinstalled programs to another hard drive, and moved much of 'My Documents' there too, in order to free up space, as L5 now takes up 24GB on its own, almost the same as Windows 7.

John Duffy

https://community.logos.com/discussion/comment/513190#Comment_513190

The crashes seems to always be coming from the HistoryManager component, so I have two suggestions.

1. Don't open the History panel. This should avoid the code path that is leading to the crash. Hold down the CTRL key at startup to show the Sign In dialog, then check the "Use blank layout" checkbox before clicking Sign In. You will also need to avoid loading layouts that include the History panel.

2. Delete the history database. This will lose all your local history. This file can be found at "C:\Users\John\AppData\Local\Logos4\Data\aytx5cbw.n5q\HistoryManager\history.db".

If it's still crashing after doing one or both of these, please post more logs.

Hi Bradley, thanks for responding.

I'll try both and see what happens. After deleting the history.db it was reinstated at next startup by synchronising the history data with that from the cloud. I'll see what happens without the history tab in my main layout, though.

Increasing the hard drive free space seems to have helped a bit this evening.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/513213#Comment_513213

I'll try both and see what happens. After deleting the history.db it was reinstated at next startup by synchronising the history data with that from the cloud. I'll see what happens without the history tab in my main layout, though.

I realised this after making my post, but didn't get back here in time to edit it; sorry for the confusion and incorrect information.