Twice in a row, same crash after updating to Beta 4. Log files attached for both crashes.
7028.LogosIndexer (9).zip
3225.LogosCrash (4).zip
BTW: if there is a fix, it would be nice to know.
Thank you for your help in bringing this to our attention. We are aware of the crash and are currently investigating a solution. I currently don't have a work around.
We have removed the Beta 4 update as a precaution to avoid this happening to more of our beta users. We will be releasing an update as soon as possible.
Can you be more specific as to what caused the crash. I already have Beta 4, and would like to avoid the steps that produced the crash.
Hi Steve;
I was in the process of compiling log files in response to Mark's post (I have the issue also) when I see that you are already aware. I will add the following which may help in tracking down the issue. Note that the memory usage increases continually. The CPU usage remains constant at around 52. The crash (for me) occurred upon upgrading to Beta 4 and running the text comparison tool. Thanks
Text comparison is working for me.
Hi Lynden;
Try running text comparison on an entire book, such as Genesis.
No way. I have an Ssd, and I would be reluctant to do that. My stingy 4 GB of Ram would protest. Thanks for telling me what not to do.
If you haven’t crashed within two minutes of opening the software, you are not affected.
I... think that might actually be expected memory usage for that size of a comparison. TC wasn't really intended to run entire books at a time.
I believe there is a case to investigate this, and I'll check. That said, this is a different issue than Mark's.
Can you be more specific as to what caused the crash. I already have Beta 4, and would like to avoid the steps that produced the crash. If you haven’t crashed within two minutes of opening the software, you are not affected.
It's a problem with indexing user documents, which could happen around two minutes after editing any user document.
Thanks Andrew.
Try running text comparison on an entire book, such as Genesis. No way. I have an Ssd, and I would be reluctant to do that. My stingy 4 GB of Ram would protest. Thanks for telling me what not to do.
You're welcome, Lynden. [:D]
Considering what I just read (further down the thread), even if you had 8GB, it would probably have a similar effect.
Try running text comparison on an entire book, such as Genesis. I... think that might actually be expected memory usage for that size of a comparison. TC wasn't really intended to run entire books at a time. I believe there is a case to investigate this, and I'll check. That said, this is a different issue than Mark's.
Thanks Dylan for the clarification. I just realized the issue when upgrading to Beta 4 and running TC. On that note, it may have been a issue before Beta 4. I'll jump off the post now to keep from contaminating it with a different issue. [:)]
Or without editing a document at all, which was my case.
This should be fixed in 6.5 Beta 5.
Fine. Is that imminent or next week? Love to have Logos working on my laptop again.
(Also, is the Beta 4 release still held back because of this?)
Is that imminent or next week?
My question was answered before I asked it. Sorry. This thread was above the announcement thread.
Thank you for the fix. Because the Beta 4 issue prevented Logos from downloading the full update before it crashed, I had to install from scratch. I used method Two found here. Everything seems to be back in order now.
