Closed Logos after opening locator bar on a resource and it crashed on restarting. Repeatable, even when opening with a blank layout. It will start in Offline mode, though.
24506.Logos4Error.log
3201.StartCrash.zip
Still will not start normally.
Hi Dave,
I'm sorry for the inconvenience. You're saying that after having closed the Locator Bar on a resource opening Logos 4 results in it crashing every time (even opening to a blank layout)? Are the logs you posted representative of you opening to a blank layout or opening Logos 4 as you normally would?
The crash is in a logging statement (but I can't see from the relevant code why it would be a problem). Does it still crash if you disable logging?
It opens normally when logging is disabled!
EDIT:
Updated to SR-3 after starting and it will now start normally with logging enabled. Does this have anything to do with the rather unclear statement that SR-3 "Fixed bug which caused hang if user attempted to sync an edited item to which the user no longer had access."?
No, the crash is in a line of logging code that a) is executed at every startup, and b) literally hasn't changed in five months. I have no explanation for why it was crashing. Now that you have SR-3 (which has replaced your Logos4.exe file), try enabling logging again and see if you get the same crash.
That cryptic release note refers to the (hopefully unlikely) case of deleting document X on machine A, while "simultaneously" editing it on machine B. When machine B tried to upload its changes to a document that had been deleted on the server (via machine A), it could hang. We found this in internal testing and don't know of any occurrences affecting actual customers.
Now that you have SR-3 (which has replaced your Logos4.exe file), try enabling logging again and see if you get the same crash.
As I reported earlier, Logos4 (SR-3) will now start with logging enabled. Something has changed between SR-2 and SR-3 as it still crashed a matter of minutes before the update.
Sorry, I didn't read your previous post thoroughly enough.
I agree that something has changed. I also posit that if you were running SR-2 (with logging) successfully, and then suddenly were not able to run SR-2, the "something" that changed was data corruption (of Logos4.exe) on your machine. As I reported earlier [:)], the crashing code was a logging line that executes on every startup, and the crash can't be explained by looking at the relevant code (which hasn't changed between SR-2 and SR-3; the only side-effect of installing SR-3 is that all Logos 4 binaries get replaced, even if the only change is their version number). It may be worthwhile to run a full chkdsk (checking every physical sector) to make sure your hard drive isn't experiencing data corruption issues.
It may be worthwhile to run a full chkdsk (checking every physical sector) to make sure your hard drive isn't experiencing data corruption issues.
The SSD is new but I ran Intel's Full Diagnostic Scan which checks every LBA for hard errors and also does a Write/Verify check on free space. No problems!
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
