I did a search for "Plato" in the top command bar on the main page as I was looking for a timeline map that shows Socrates, Plato, Aristotle... and CRASH.
I am at a Starbucks so internet is slooooow. But no idea what happened.
The log file you provided isnt what we need. Also, please don't ever paste logs into the forum. Attach them with the paperclip icon. Please enable and post logs. See the link in my signature line.
Also, if you are able to edit your previous post, please delete the log.
I will delete my previous post. However, if I thought I was expecting a crash, I would have the logging tool open. Users should never have to use that tool... so it wasn't open.
So for you and your request, I will remove my post. And if I experience another crash, I will try to log it. But that's not my job. It shouldn't be my job and I am not happy my crash will go unaccounted. So good luck to anyone else experiencing this bug. So far, V6 is more pain than pleasure. Certainly the utility it should provide is overshadowed with one of the worst experiences I've ever had with a piece of software.
Well, I couldn't edit OR delete my post. Only options are reply or more (Report Abuse, Add post to Fav, Add this forum as a Fav... no edit method.). Perhaps an admin can do so without labeling it abuse b/c I didn't know posting an Apple crash log as text was inappropriate. Other forums collapse the post if too long for others trying to read.
I did want to follow up that Logos gave me a crash report message box upon restarting the program today. Here's the message.
Hope this helps.
Dave
if I thought I was expecting a crash, I would have the logging tool open. Users should never have to use that tool... so it wasn't open.
You don't understand the tool apparently. The logging tool allows you to:
This system really is very simple.
And if I experience another crash, I will try to log it.
As I just said above, if you use the tool to turn logging on, it will be on when you experience a problem. You don't have to have the tool open... Just "enable" logging via the tool, then close it. Once you experience a crash, open the tool and press the "archive" button BEFORE you restart Logos. It will place all of the various log files into a zip file on your desktop.
So good luck to anyone else experiencing this bug.
I have no idea why Logos crashed for you. There may be a bug, or you may have a corrupted database file. We won't know unless we can see the log files. If you can't reproduce the issue, then good, right?
FWIW - I am not having problems with crashing. There is another issue with some users (including myself) with dreadfully interrupted downloads... but that is another issue altogether.
You're right. I don't understand the logging tool. It's not clear how it works. Take a look at the main screen - with fresh eyes.
The message it shows when the Logos application is closed should be fixed/updated.
Suggestion:
If Logos unexpectedly closed during the last session, Click Archive Logs now to save the report and submit the log for technical assistance.
You must restart Logos BSV6 for changes to take effect.
***Guess they can add that to their list of improvements. Oh and see how BOTH sample and Archive Logs buttons are greyed out - communicated you cannot click on them. Minor but major for proper UI/UX. Again, another "check the manual" item... Looks so "Windows" too
My log would have been running during that crash then... but if as you say is true, the data may have been wiped the few times I tried reopening afterwards. Attached for reference. That one MAY contain another bug I may have discovered during the crash - could have been related. It's from a bad internet connection. Logos is trying to connect via internet to their server and they don't let the process time out quick enough. It MAY have connection when it tries... but then it can't handle say the sync or homepage updating and it hangs. Hung this morning for 3-4 minutes before I moved computer closer to the connection and restarted program. Again, that should not happen. I am bringing that up for international users who I can only imagine have worse speed issues than we do stateside.
8206.LogosLogs.dgeipel.20141107-140356.zip
***BTW - I too had the issue you've been having - since the first day V6 went live. I posted my issues right away but no one @ the company seemed to pick up on it. https://community.logos.com/forums/p/93043/645511.aspx#645511
Thanks for the feedback. Hoping they get their ducks in a row and get some of these issues resolved.
How large is your hard drive? How much free space?
According to logs it was 250 MB when the indexer crashed a while back. Now it stands at 3078 MB which is still insufficient for indexing with a 3 GB index! Free space should be at least 20 GB.
Wow. Did I actually read the log file right? [:o]
Thanks Dave. It's almost like I need to dedicate my computer to Logos. What a beast (in a positive sense). That's why I believe their indexing needs improvements. Doesn't appear they did anything to address it. Perhaps that's why I had the crash.
I really think they need update their short term warning message.
1) Why doesn't it look at available resources and determine 5GB isn't enough to index?
2) Why do they throw an incorrect warning (notice they say atleast 1GB when you're saying "Give me 20... or die", well maybe "or I'll show you"?
Bottom line is that I am fighting against a methodology and programming approach that I may fight against as long as I use the program. There has to be a better way and it's not what they are doing today.
So if it's a space issue, tell me I cannot update until I make room for the program to REINDEX (for the upteenth time).
I have 5GB (out of 256gb) free. I've been told I need to give the program more space but that's not what the program states: Logos says I only need atleast 1GB free.... in the warning message.
Seems to me that should say 20GB free based on feedback. UGH.
Doesn't appear they did anything to address it.
Indexing improvements actually ARE a part of L6.
Why doesn't it look at available resources and determine 5GB isn't enough to index?
That is an interesting question / thought.
Our advice isn't a Logos one, but rather a "philosophy of hard drives". It is MORE important on traditional hard drives to "give them room to breath," but it is true of SSD's as well. Cramming isn't good for hard drives, washer machines or suit cases. [;)]
