Zac - I am not experiencing the same difficulty that you are. Why don't up upload a log - (learn more HERE). After you have done that, can you try using a completely blank layout and opening the resource? This would help you to discover if there is something else causing your computer to crash (like the info panel, or explorer, etc).
BUG: Resource Causes Logos 4 Hang
Zac
Member Posts: 24 ✭✭
Just wanted to report a bug with Logos 4 Mac:
Whenever I open Word Biblical Commentary, Volume 44: Colossians, Philemon, I can scroll around and go to many passages, but when I try to go to Colossians 2:9 or any of the passages immediately following, Logos hangs and starts consuming 100% of my CPU (I'm on a dual-core so it basically eats up half of my CPU). I can't get it to respond and end up having to Force Quit the program.
Any idea what could be causing this or how I can fix it, or do I need to wait for a program update?
Hardware Configuration:
MBP 2011, 2.3 GHz Core i5, 8 GB RAM, and 187 GB free space on my HD.
OSX 10.7.2
Logos Version:
4.3 SR-6 (4.30.0.1613)
0
Comments
-
Zac - I am not experiencing the same difficulty that you are. Why don't up upload a log - (learn more HERE). After you have done that, can you try using a completely blank layout and opening the resource? This would help you to discover if there is something else causing your computer to crash (like the info panel, or explorer, etc).
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Here's the log I pulled out of the Console. There's also a file under Diagnostic and Usage Information that I can post if that is helpful. I can pull that and post it as well. I started it with a blank layout and the resource still crashed it.
0 -
Update: I deleted the volume from my resources folder and re-downloaded it from the server, and the program still hangs when trying to access Colossians 2:9. Any idea what's up?
0 -
Zac,
What panels do you have open? Just the WBC? Can you turn off all the visual filters (highlighting, notes, reading plans, etc) in the WBC and see if that works?
Tom
Mobile Development Team Lead
0 -
It'll hang even when WBC is the only open panel, and it hangs even when all visual filters are off. [:S]
0 -
Zac,
By default, logging is not turned on in 4.3, so if you hold down Cmd when you are launching the app and then navigate to Col 2.9 in WBC and then post the logs, we'll have a better picture of what's likely going on.
(As a side note, the error in your original log is innocuous and not related to the crash you're seeing).
Tom
Mobile Development Team Lead
0 -
Tom,
For some reason I can't get it to log. When I hold Cmd and the sign-in window pops up, I've gone through it signing in normally and through using a blank layout. For some reason it's not recording any logs.
Also, it's not actually crashing out or anything. The program just hangs and isn't responsive until I force quit it, so it won't generate a crash report.
I took a sample of the process in Activity Monitor while it was hanging. Maybe that will help?
5327.Sample of Logos Bible Software 4.txt
0 -
Zac -
Did you visit the wiki link for logging that I gave you earlier? I will post it again below. Also, if you have Lion, you will need to unhide your user library (it is hidden by default in 10.7). To temporarily show it:
- From the finder menu, click "go"
- While in the "go" menu, press and hold the option key. The library will display.
- Click on library and its folder will open for you.
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
From the sample you posted it looks like it's a core text Mac rendering bug that we've seen a few times.
If you change the font size of the WBC panel, or resize your Logos 4 window, then navigate to Col 2:9 does the problem still occur?
Mobile Development Team Lead
0 -
Tom Philpot said:
From the sample you posted it looks like it's a core text Mac rendering bug that we've seen a few times.
If you change the font size of the WBC panel, or resize your Logos 4 window, then navigate to Col 2:9 does the problem still occur?
I tried changing the font size in one instance, and resizing both the resource window and the logos 4 window in another instance, and both times resulted in a hang.
I got a log. I've been holding Cmd but forgot to hold it until the sign in window appears. That's why it wouldn't take any. I haven't looked at it at all, but I hope it contains something that's helpful. Thanks for all of your help.
-Zac
0 -
Any insight into this log?
0 -
Zac said:
Any insight into this log?
Looks like Col 2:9 reference appears 5 lines before end of log.
Wonder about upgrading to Logos 4.3 SR-7 and restarting Mac, then use 5504.Logos4MacLogging.app.zip to display logging setting, change to enable logging. Launch Logos 4.3 SR-7, repeat hang condition with Col 2:9, wait a minute (to verify hang does not go away), then use Logos Log Scribe to create zip file of Logging folder (that automatically includes a copy of console messages), followed by replying and attaching zip file (on your desktop).
Keep Smiling [:)]
0 -
Well, took me forever to get back to this. I finished the assignment I was working on and set Logos aside for a while. Now I'm working on a sermon and am having trouble with a commentary on the Pastoral Epistles.
Here's the log:
0 -
This is happening a lot when I use Word Biblical Commentary resources. I don't know if it's a resource error or if it's a program bug. I appreciate all of the help in getting this sorted out.
0 -
Zac - I don't read logs, but thought I would ask a quick question that others might ask: What version of Logos are you now using?
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Zac said:
Here's the log:
Puzzling: Logos4.log entries abruptly end at 19:59:02 while Console Messages show 43 seconds later: "Exited: Terminated: 15"
Wondering if force quit was done ?
Also wonder if program scaling being used since some errors earlier in Logos4.log have font size 13 ? Edit: for AlberNew font family.
Keep Smiling [:)]
0 -
Zac said:
This is happening a lot when I use Word Biblical Commentary resources. I don't know if it's a resource error or if it's a program bug. I appreciate all of the help in getting this sorted out.
Hi Zac,
Can you please update to 4.3 SR-8 (the current release) and see if the problem still occurs?
0 -
Alright, I'm using 4.3 SR-8, and the problem persists.
As far as Force Quit, it is necessary for me to perform a Force Quit every time the problem occurs, since otherwise the program hangs and will not respond at all. It won't quit or crash, it just sits there processing something (using 100% of CPU on a dual-core with hyperthreading--about a quarter of the CPU).
I'm not sure what you mean about font scaling, Keep Smiling... I am not sure how to tell whether it's on or off.
Thanks!
0 -
Zac said:
Alright, I'm using 4.3 SR-8, and the problem persists.
Zac, I cannot reproduce what you are seeing on any of our test systems. Have you tried using a different font in Program Settings to see if that alleviates the issue?
0 -
Zac said:
I'm not sure what you mean about font scaling, Keep Smiling... I am not sure how to tell whether it's on or off.
Program scaling is always on. Curious if program scaling is not 100 % (Logos recommended value).
Wiki has Mac Troubleshooting => Program Scaling
Option: download 1373.Logos4MacDisplayScale.app.zip to show, then can change Program Display Scaling to default 100 % or custom %
Keep Smiling [:)]
0 -
Alright everyone, I think the problem has been resolved. Thanks for the help. The issue is with the SBLGreek font. When I switched back to the default Greek font (Gentium) everything worked fine. I guess Logos has an issue with SBLGreek.
Keep Smiling, the program scaling was set to 100%. Thanks for all of your help.
It's good to know I can use all my resources without hassle again.
-Zac
0 -
Zac said:
The issue is with the SBLGreek font. When I switched back to the default Greek font (Gentium) everything worked fine.
Thanks for reporting this, I was able to reproduce the issue. I've written up a case and sent it to our Development department.
0 -
This issue should be fixed in 4.5b Beta 1 (or when 4.5b ships to the stable channel for stable users.)
0
