The program opens up. Works for about 2 minutes and then crashes. Restarted computer same thing. Tried indexing library same thing.
Hi Trent - and welcome to the forums
Sorry to hear you are having problems.
Which version of Logos 6 do you have - and running on which platform?
Please enable diagnostic logging and post logs in a reply to this thread after a crash - details at https://wiki.logos.com/Diagnostic_Logging
Graham
I am having the same type of problem, though the average time before the crash is longer than two minutes. I have attached my log files.0218.LogosError.zip
I'm a little surprised to have gotten no reply from Logos since my post two days ago. The software is practically useless to me because it crashes every time I try to use it for more than a few minutes.
I have tried just leaving it open, and it seems that if I am not actively using it, it will not crash. But when I am scrolling around through Bible text or clicking on links in my word study window, the crash occurs seemingly at random, but it happens every time I work for more than a few minutes. I have had Logos 6 for a long time, so I'm guessing this is related to the recent major update from Microsoft Windows or possibly a recent update to the Logos 6 software. But something is definitely wrong, and I really need it sorted out soon.
It is difficult for me to get on the phone with tech support, but I will try to do that next unless someone suggests a fix. There appear to be several people affected by the same issue, so I wonder if the Logos dev team has been able to recreate the issue and, if so, if they are working on a fix already.
I'm a little surprised to have gotten no reply from Logos since my post two days ago.
The forums are primarily a user driven means of support. If you need help from Logos, you need to either call or send an email (although the later is generally the worst way to get help unless you have someone's direct email address).
There appear to be several people affected by the same issue, so I wonder if the Logos dev team has been able to recreate the issue and, if so, if they are working on a fix already.
"The same issue" is hard to diagnose. Just because you are experiencing similar symptoms, does not mean that you have "the same problem." If you need help in the forums, it is best to create a new thread, explain your issue clearly, and provide adequate details. This is necessary because 1) it might not be the "same issue" and 2) it is rude to interrupt someone else's thread.
Alabama24,
Based on my own perusal of the forum posts, over the last few days there has been a noticeable uptick in the number of people complaining that Logos is crashing after having used it for a while, with no apparent cause. Certainly that could be a coincidence. But it doesn't seem likely to me.
Since this is a public forum, I'm not sure how it can be rude to add my own content in the form of additional error logs and comment about identical or extremely similar symptoms. Besides, I posted two days after Graham's reply to Trent, and Trent had not posted his own error log. Rather than start a new thread, I wanted to keep this one alive by adding my experiences to his, since they are so similar, and I wanted to give a log history for Graham to work with, since Trent had not done it yet.
My surprise in not hearing from a Logos representative is primarily due to past experiences in which someone from Logos has replied within one business day when I have posted problem reports on the forums in the past. So if I have an unrealistic expectation in their attentiveness, it is in part their own fault for being so prompt in times past. Also, as I pointed out in the last sentence of my earlier post, I have a hard time getting on the phone with Support during their hours, so this forum is the best tool I have for reaching out for help apart from the generic support email which, as you yourself pointed out, is not an ideal method.
Rather than start a new thread, I wanted to keep this one alive by adding my experiences to his, since they are so similar
I know it wasn't your intent, but it is rude (or at least counter-productive) to jump in on someone else's thread. I know it's not the same thing, but how would you like it if you were visiting the doctor and someone knocked on the door and said, "Hey! I have the same problem!" [:)] You deserve personalized attention... so does the person who originally posted. Please create a new thread.
I know you think that... and it may indeed be "the same thing." But you don't know that. If you knew that, you would also know what the problem was and how to fix it. I don't know what the problem is, although my level of technical skills is fair to midline.
My surprise in not hearing from a Logos representative is primarily due to past experiences in which someone from Logos has replied within one business day when I have posted problem reports on the forums in the past. So if I have an unrealistic expectation in their attentiveness, it is in part their own fault for being so prompt in times past.
I am certainly glad for FL's help in the forums, but as I said earlier, the forums are primarily a network of user support by fellow users. If you create a new thread and if no one jumps in soon, I will try to flag someone down from FL.
Alabama24, Based on my own perusal of the forum posts, over the last few days there has been a noticeable uptick in the number of people complaining that Logos is crashing after having used it for a while, with no apparent cause. Certainly that could be a coincidence. But it doesn't seem likely to me. Since this is a public forum, I'm not sure how it can be rude to add my own content in the form of additional error logs and comment about identical or extremely similar symptoms. Besides, I posted two days after Graham's reply to Trent, and Trent had not posted his own error log. Rather than start a new thread, I wanted to keep this one alive by adding my experiences to his, since they are so similar, and I wanted to give a log history for Graham to work with, since Trent had not done it yet. My surprise in not hearing from a Logos representative is primarily due to past experiences in which someone from Logos has replied within one business day when I have posted problem reports on the forums in the past. So if I have an unrealistic expectation in their attentiveness, it is in part their own fault for being so prompt in times past. Also, as I pointed out in the last sentence of my earlier post, I have a hard time getting on the phone with Support during their hours, so this forum is the best tool I have for reaching out for help apart from the generic support email which, as you yourself pointed out, is not an ideal method.
Geoff, your logs don't show a crash. Could you replicate the crash, but don't reopen Logos until after you've grabbed the logs. Please zip and upload everything in the logging file.
The conversation moved to THIS thread.
Geoff, your logs don't show a crash. Could you replicate the crash, but don't reopen Logos until after you've grabbed the logs. Please zip and upload everything in the logging file. The conversation moved to THIS thread.
Thanks Alabama!
