Logos 5 Stops Working
When I try to un-maximize the window to move it around the program freezes. It seems to be related to the program trying to re-populate the resources that are open on the screen. Attached are log files.
Comments
-
Having the same issue.
0 -
actually, when the program starts, it covers about half screen. When I try to re-size, it crashes the program altogether.
0 -
This appears to be a common issue in this release:
http://community.logos.com/forums/p/68313/475258.aspx#475258
I would follow the recommendation in the thread above and call tech support (800-875-6467) to get the work around for issue.
0 -
Welcome to the forums! Sorry you (both) are having troubles. [:S]
I am not a full fledged "techie," and was unable to glean anything from your logs. (Good job of posting them, by the way).
Have either of you tried to load to a blank layout? Press and hold down the control key immediately upon startup, then check the appropriate box.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Randy W. Sims (Shayne) said:
This appears to be a common issue in this release:
Randy - Why do you think this issue is related? The error message from the other log was "Error ID: 5027," which isn't to be found in these logs. Also, the other thread makes no mention of resizing any windows. Did I miss something?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Marvin Mitchell said:
when the program starts, it covers about half screen. When I try to re-size, it crashes the program altogether.
Marvin - If loading to a blank layout doesn't fix your issue, please create a new thread, explain the issue as best as you can, and post logs. Instructions can be found in my signature line.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
alabama24 said:Randy W. Sims (Shayne) said:
This appears to be a common issue in this release:
Randy - Why do you think this issue is related? The error message from the other log was "Error ID: 5027," which isn't to be found in these logs. Also, the other thread makes no mention of resizing any windows. Did I miss something?
In both cases, the LogosCrash.txt file lists the Error ID: 5027 and the last entry in the LogosError.log file, the most recent entry, shows the same error with a similar stack trace. From the trace, it looks like the crash is occuring in the RichText control any time the window is redrawn-that would occur when the window is resized or when it is drawn for the first time on startup, etc. I'm curious what the work around they mention is. Maybe a reg switch to change to the old control?0 -
Randy W. Sims (Shayne) said:
From the trace, it looks like the crash is occuring in the RichText control any time the window is redrawn-that would occur when the window is resized or when it is drawn for the first time on startup, etc. I'm curious what the work around they mention is.
The crash is associated with generating Home Page content from RSS feed, so the workaround is to avoid the Home Page e.g. start with a blank layout and switch to loading a layout when Logos starts. Resizing a Home Page window will regenerate content and cause a crash, whilst resizing a layout window doesn't regenerate any content.
Dave
===Windows 11 & Android 13
0 -
Thanks for explaining that. I believe I understand better now, looking again at the logs. Looks like it may depend on specific content as I wasn't initially seeing the crash, but now I am. It seems to be eliminated by disabling the Logos Blog on the home screen (Verbum Blog shows no effect). Disabling all options on the home page except Logos Blog brings back the crash.
Seems a tad excessive to check for updated rss feeds or change the content in any way (other than layout) when resizing.
0 -
Hey guys, sorry about the trouble.
It appears this problem is coming from the Logos Blog. We're unable to resize the blog at the moment, resulting in a crash. If you open Logos to the home page, click "Customize" and uncheck "Logos Blog" before resizing the window, you should be okay.
I've notified development and we hope to have this resolved soon, but we may not have it nailed down until after Easter weekend.
0
