-
Jack, Your logs indicate that this might be another "corrupt index" issue. We haven't had any other similar reports, so I wonder if there is a bug triggered by some content in one of your documents. Generally a corrupt index would most likely be caused by a system failure of some kind, but considering that this has recurred with the same document specific
-
Jack, It looks like this is a very similar crash to the one you reported here: https://community.logos.com/forums/t/187983.aspx Did rebuilding the index seem to improve the situation at the time? e.g. did you notice a decrease in frequency of crashes? I'd like to try to narrow down if this is a corrupt file issue (possibly caused by our code, considering
-
Jack, It looks like you might have a corrupt index file. I think the best way to attempt to resolve this issue would be to execute the `rebuild index` command. Good luck, and let me know if you still experience this issue after doing so. - Matt
-
Jack, We were able to make a change that might resolve this hang. The change shipped with RC 1, so let us know if you continue to experience this issue. Thanks! - Matt
-
Jack, This looks like it might be a corrupted database/index issue. We should try to rule that out, first. Do you mind renaming the directory at `/Users/jackcav/Library/Application Support/Logos4/Documents/fwu3dehb.5cn/Documents` to `Documents~backup` (or, similar) and reporting back? If this does fix the issue, it might be interesting to see what the
-
Jack, The hang that you keep running into is a very unfortunate problem. Logos has been shipping with code that attempts to mitigate this same problem for years. Most users might experience this hang on occasion, but it does seem to be extremely consistent for you (each update, which you get weekly from the beta channel?). I've been looking for a solution
-
Jack, Thank you for the report. It looks like this was an instance of a known issue with Mono that we are unable to resolve at this time. As far as we know, it is a "random" hang, but is more common after an application update. - Matt
-
Michael, Thank you for submitting logs. Unfortunately, I wasn't able to find any relevant messages in them. I sent you a message via Faithlife Messages with some steps to send additional information (privately) to continue diagnosing the problem. Thank you. - Matt
-
Mark and Justin, I'm sorry to hear that you are both experiencing this issue :( Would it be possible to reproduce the issue with logs and post them here? Thank you. - Matt
-
Michael, I'm very sorry to hear you're having these issues and have lost time due to these bugs. I haven't been able to find any logged server errors from your account. The last revision of the template in question was made on 3/16, which I'm guessing is a version submitted before all the changes that you lost. Is there a chance you can reproduce the
-
Micah, Sorry to hear you're having a problem. From your logs, it looks like you might be experiencing this problem as a result of a file permissions issue. I'm not sure how familiar you are with macOS file permissions, but the gist is that each file and directory specifies which system accounts have read/write access. It's not unheard of that permissions
-
Cindy, I'm sorry to hear that you're having issues. This is definitely odd behavior. Would you mind posting logs and the workflows.db file? If you'd like to avoid posting the .db file publicly, you can email it (or a zipped version of it) to me directly at matt.preucil@faithlife.com . Additionally, it might be useful to copy the .db file in both pre
-
Tim, Sorry to hear you're having issues. We did a quick look at your Notes activity and it looks like your workflow notes are in the "trash"... You should be able to restore them from the Notes Tool by "untrashing" them. As for how/why this happened, I'll look for any factors that might have caused this. Is there anything you are aware of other than
-
Thank you for the report. This issue will be fixed in an upcoming release, and all the existing notes without a style will be migrated to use the default style. - Matt
-
Patrick, It seems like you might be experiencing the same issue I recently posted about in this thread: https://community.logos.com/forums/t/174611.aspx - Matt
-
Matt, We recently had another customer call in experiencing this same problem. A fix will ship in the next release (likely SR-2). I believe this issue might have been caused by, on Windows, selecting a "copy to" location in the Thematic Outlines guide section that isn't available on Mac, and there is a bug that causes a crash here. Does this sound like
-
Steven, Your logs indicate that you might be experiencing a bug we've had with case-sensitive file systems on macOS. A fix for this will be shipping soon in SR-1. If you'd like to confirm you have a case-sensitive file system, you can open Disk Utility, right click on the drive, and click 'Get Info'. If 'Is case-sensitive' is 'No', and/or if this issue
-
Michael, As Alan mentioned, you might benefit from the changes we're rolling out soon. In the meantime, you can test if this fix will work for you by: - Going to app.logos.com and opening Atlas. I would expect a crash here. - Going to chrome://flags and enabling "ignore-gpu-blacklist" and restarting Chrome. - Going back to app.logos.com to see if Atlas
-
Michael - Thanks for being on the lookout! We updated one of our dependencies (CEF) which unfortunately has a nasty bug that causes this in the version we updated to. It looks like we should be able to patch this behavior, and hopefully that fix will ship in the next beta. - Matt
-
[quote user="Jack Caviness"] Confirm Indexer freeze Early 2018 27" iMac Mac OS 10.13.3 Logos 7.14 Beta 2 Activity Monitor Sample 3771.Sample of LogosIndexer.txt [/quote] Sorry, Jack, I missed seeing this indexer sample.