After updating to A20, the UI is unusable. It is highly unresponsive (i.e. spinning beachball 80% of the time... for 1-5 minutes at a time) and often fails to shut down. In the attached logs all I did was:
That means it takes me 30 mins to start and stop logos 4 mac. Logos Mac v1 (Libronix) takes less then 10 seconds to do the same thing.
Thanks,
Mike
p.s. there is no downloading or indexing occuring via the menu bar icon that I've seen
1641.beachballparty.zip
According to the logs, it wasn't done syncing.
It looks like it stopped because you closed the app while it had a week or so remaining (assuming the was stuff to sync between 5/15 and today).
I'll look into why syncing is such a major drain on performance.
One suspects that if you let syncing finish completely, you won't have that issue continually.
Director of Engineering for Enterprise and Operations
I'll let it run for a few hours today.
As a side note, I also have it on my windows desktop and my windows VM on the mac... neither have this issue (nor seem to be taking so long to sync)
I started Logos 4 Mac up at 9:20am local time and left it running until 3:30pm local time... well actually... it is still "running" with the spinning beach ball it's ever present friend. Spiking CPU intermittently... how much longer should I let it run? 0434.neverending-beach-ball-sync.zip
Cameron Watters: According to the logs, it wasn't done syncing. It looks like it stopped because you closed the app while it had a week or so remaining (assuming the was stuff to sync between 5/15 and today). I'll look into why syncing is such a major drain on performance. One suspects that if you let syncing finish completely, you won't have that issue continually.
OK, I've come to the (possibly faulty) conclusion that things are never going to finish syncing. This last run, 15 min shy of 12 hours of letting it run to finish sync, the UI soaked 100% CPU for hours on end and the UI was utterly unresponsive and stuck in spinning ballon state for the last 3 hours of waiting.
I've attached the 2 logs as well as a cut and paste of the stack dump: 0245.logsandstack.zip
Next step?
Mike,
I am having the same issue. I let it sync for about 6-9 hours then the program becomes usable (cpu runs about 100% during this time). However, when I close it down, it will not close but only give me a spinning pizza. Good luck finding the problem (I attached logs of this previously).
Michael Hatcher
visit: www.bellviewcoc.com
iMac 2.8 GHz i7 quad core, 8 GB Ram, 1 TB HD
For me, I have twice gotten the beachball situation (since getting A20) while trying to read a Bible reading plan. It's not doing this every time, but basically when I try to mark the passage as read, Logos crashes. I have to force my Mac to shut off (by holding down the power button) because there's no other way to reboot. I look forward to being able to continue my reading plan without dealing with all of this. It's really defeating the purpose of having quiet time with God. I mean, after quiet time, I normally feel better, not worse. :-P Ok, maybe I should review Ephesians 6:10-20 again. :-)
Andy Warmack: I have to force my Mac to shut off (by holding down the power button) because there's no other way to reboot.
Why do you need to reboot just because L4 crashes? This should not affect other applications or the OS. If you need to force quit L4, hold down Command-Option-Escape and select L4 from the dialog box that will appear.
Enable-and-Submit-Log-Files | Install
I see that I left out that part. The answer to why I need to reboot is because I literally can't force L4 to quit since it will NOT close in this situation. Force Quit has no effect. In fact, I cannot even shut down or reboot because L4 just keeps running and running. I have to force the entire computer to shut off (and I hate having to go that far).
Mike S.:
Has you computer gone to sleep during this whole process?
No. My default for plugged in is no sleep... ever.
Before I ran this process I rebooted and did nothing else. (other then post via safari to this forum)
Mike S.
Are you on a wireless network?
yes, exclusively during the time of the logging.
I HAVE run it (with the same results) on a wired network as well.
Someone in tech said they experienced someone getting a similar issue but when resetting their wireless router it fixed it. Perhaps resetting that and maybe even your primary router may give us a different result.
I'll attempt that along with a reboot and get back to you with results in an hour.
No apparent luck. Turned off wireless, Shutdown, Reboot router, wait for router, Startup, Start Logos... for about 5 min, normal sync seems to be occurring with the spinning sync icon, then goes into spinning beach ball mode... I'm letting it run... logs look exactly the same. Keeps restarting sync after about a minute and app hanging.
While my tail of the log file is cranking along... syncing the same stuff over and over, the UI is no longer responsive at all.
Anything you'd like me to try next?
Mike S.: Anything you'd like me to try next?
Would you be willing to zip up and upload the contents of
/Users/<your username/Library/Application Support/Logos4/Documents
I'm wondering if there is potentially some corruption in the sync state data.
Is there an email I can send it to? I've tried sending a zip file to your email based on previous emails with others in Logos. Please let me know if you don't get it. . . actually.. just got mail delivery failures based on restricted addresses. Please let me know some more private way then forums to share the zip file.
What is happening to you sounds just like what happens with mine. Start Logos and let it run for about 6 to 10 hours straight, then see if it works all right. If I do this, my Logos seems to work fine, otherwise about all I get is the spinning beach ball. (Start it before you go home and let it run all night, then see if it works the next morning.) However, realize that if you close down the program, you will probably have to go through the same thing again when you start it the next time (the 6-10 hour wait).