Logos Progam Freezing After March 4 Update to Resources
Since the March 4 update to Logos 4 for MAC, I have noticed that the LOGOS program has been freezing fairly often, even when only one resource is open. This requires user to Quit or Force Quite Logos and reopen.
Comments
-
Apologies - unable to replicate - please elaborate which resource and reference. Sometimes, a particular resource can be problematic (during Logos 4 Mac alpha pre-releases, remember encountering a few resource specific issues). Also, Logos 4.2a needs to rebuild indexes - wonder if indexing complete ?
Mac Troubleshooting page has How to Report Bugs in Logos 4 Mac - screen shot of open resource that precedes freeze would be helpful - after a Quit and before reopening Logos, please post compressed file with logs. Every time Logos is opened, log contents are overwritten.
Keep Smiling [:)]
0 -
It seems to a general --and is happening with many resources, although I first noticed it in the Finney library. Unfortunately no log is available. The freezing usually happens several minutes after the resource is opened, do you think that would occur if the indexing were incomplete?-
0 -
Jim Gilmore said:
It seems to a general --and is happening with many resources, although I first noticed it in the Finney library. Unfortunately no log is available. The freezing usually happens several minutes after the resource is opened, do you think that would occur if the indexing were incomplete?-
Searching my library finds 6 Finney resources - please elaborate resource(s) that are freezing - resource name with chapter or page would be appreciated (easier to try replicating).
Indexing incomplete is a possibility plus more - log files have informative messages. After next freeze and before launching Logos 4 Mac, please compress and post log files => Mac Troubleshooting page has How to Report Bugs in Logos 4 Mac section with steps to compress and post files. Section also has link to Logos Log Scribe - assist with compressing files.
Logos 4 Mac has diagnostic logging messages always enabled (that include crash messages, which is another possibility) - cannot tell without log files.
Other option is contacting Logos => http://www.logos.com/about/contact Technical Support available by phone Mon - Fri from 6 am to 5 pm Pacific (with your permission, can remotely connect and look at log files, etc).
Keep Smiling [:)]
0
