BUG A20: Beach Ball Spinning Party

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:

Open Logos 4 Mac (starts at 13:19.55)
Wait until Syncing is complete (as per watching tail -f of Logos4.log file)
(attempt to) Close Logos 4 Mac (completes AFTER 13:53.14)

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

Find more posts tagged with

Comments

Cameron Watters (Faithlife)

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.

Mike S.

https://community.logos.com/discussion/comment/131327#Comment_131327

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)

Mike S.

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

Mike S.

https://community.logos.com/discussion/comment/131327#Comment_131327

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?

Michael Hatcher

https://community.logos.com/discussion/comment/131614#Comment_131614

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).

Andy Warmack

https://community.logos.com/discussion/comment/131647#Comment_131647

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. :-)

Jack Caviness

https://community.logos.com/discussion/comment/131713#Comment_131713

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.

Andy Warmack

https://community.logos.com/discussion/comment/131848#Comment_131848

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).

Thomas Ball

https://community.logos.com/discussion/comment/131614#Comment_131614

Mike S.:

Has you computer gone to sleep during this whole process?

Mike S.

https://community.logos.com/discussion/comment/131916#Comment_131916

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)

Thomas Ball

https://community.logos.com/discussion/comment/131919#Comment_131919

Mike S.

Are you on a wireless network?

Mike S.

https://community.logos.com/discussion/comment/131931#Comment_131931

yes, exclusively during the time of the logging.

I HAVE run it (with the same results) on a wired network as well.

Thomas Ball

https://community.logos.com/discussion/comment/131937#Comment_131937

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.

Mike S.

https://community.logos.com/discussion/comment/131939#Comment_131939

I'll attempt that along with a reboot and get back to you with results in an hour.

Mike S.

https://community.logos.com/discussion/comment/131943#Comment_131943

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.

Mike S.

https://community.logos.com/discussion/comment/131999#Comment_131999

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?

Cameron Watters (Faithlife)

https://community.logos.com/discussion/comment/132002#Comment_132002

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.

Mike S.

https://community.logos.com/discussion/comment/132010#Comment_132010

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.

Michael Hatcher

https://community.logos.com/discussion/comment/132011#Comment_132011

Mike,

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).

Mike S.

https://community.logos.com/discussion/comment/132163#Comment_132163

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.

Thanks for the tip and the note that this is a shared problem. If you look higher up the chain, you'll see that I've already let it run for almost 12 hours with zero change.

Thanks!

Mike

Michael Hatcher

https://community.logos.com/discussion/comment/132170#Comment_132170

Mike,

Sorry I had missed that. I would add that if the cpu was still working to continue to let it run till the cpu drops and the logs basically become inactive (there will be some activity in both but it will be very minimal). During this time (as it syncs seemingly over and over), there will be a few seconds without the spinning beach ball but just about all the time that is all you will get. After this, it should become usable---at least it has for me.

I wish I could tell you how long it will take, but might take different times for different folks. Patience is the key to it (maybe a few days of patience). (Guess I could say that I asked the Lord for patience and that I wanted it today and got....) After it becomes usable just do not close it down or you get to go through it all again (or that is how it has worked for me). Again, good luck.

Mike S.

https://community.logos.com/discussion/comment/132196#Comment_132196

I would be open to that approach if I could get some kind of technical direction along those lines. At this time, Logos seems to be thinking it might be a corruption in my Documents folder because the logs show that the sync activity is being repeated over and over and over... I'm just not comfortable putting that data out on a forum where it is forever indexed by google and all of its spidery competition and there doesn't seem to be any alternative.

I'm thinking about changing the program settings to turn off internet to see if that changes anything.

Thomas Ball

https://community.logos.com/discussion/comment/131890#Comment_131890

Andy:

If you could post logs and a description of what you were doing when the hang up occurred I can file a bug and have dev look at them. There is a link in my signature on how to post the logs.

Thomas Ball

https://community.logos.com/discussion/comment/132239#Comment_132239

Mike S.:

Check your email.

Mike S.

https://community.logos.com/discussion/comment/132255#Comment_132255

Check your email.

Done. Now check yours [:D]

Thomas Ball

https://community.logos.com/discussion/comment/132262#Comment_132262

Mike S:

Posted.

Mike S.

https://community.logos.com/discussion/comment/132227#Comment_132227

I have indeed experimented with turning off Automatic Updates and Use Internet and my problem goes away (ran it in the background for hours with no problem).

Then I decided to have a little fun. I clicked the sync icon and it chugged away for about 1-2 minutes. When completed, the sync icon came back with a Yellow caution icon with a exclamation mark in it. Otherwise, no hangs, no problem with CPU runaway, etc...

Here's the logs:

5241.use-internet-no.zip

Michael Hatcher

https://community.logos.com/discussion/comment/132299#Comment_132299

Mike,

I tried turning off Automatic Updates and Use Internet and my problem also went away (although I did not run it for very long but will try today for a longer period). Good call for a temporary fix.

Tom Philpot (Faithlife)

Mike S.

Try this, delete your /Users/msale/Library/Application Support/Logos4/Documents/0qg65fd8.zel/LocalUserPreferences folder and your /Users/msale/Library/Application Support/Logos4/Documents/0qg65fd8.zel/UserPreferences folder and restart.

This should clear up your sync issues after a full re-sync of your data.

Tom

Mike S.

https://community.logos.com/discussion/comment/132603#Comment_132603

Try this, delete your /Users/msale/Library/Application Support/Logos4/Documents/0qg65fd8.zel/LocalUserPreferences folder and your /Users/msale/Library/Application Support/Logos4/Documents/0qg65fd8.zel/UserPreferences folder and restart.
This should clear up your sync issues after a full re-sync of your data.

Not looking so great as of yet. Process has been running for well over an hour and a half and so far app behavior and the log files are nearly identical to prior to the removal of the directories. The first sync seems to work just fine, then it goes into an infinite loop and spins the CPU for a while, then it sits waiting to run another sync, then spins the CPU and does another useless sync. It did reset my preferences and create a number of SQLite DBs (prefs were set to not use internet or autoupdate). I'm letting it run overnight, but it is repeated downloading the SAME Exact batches... 14 times in 1.5 hours. There are 4 failed updates with local changes... guess what, they show up, you guessed it! 14 times.

I'm at the place where I would prefer to "start over" with my install on OS X unless I'm helping you nail down a defect.

Mike Binks

https://community.logos.com/discussion/comment/132686#Comment_132686

Mike S

I am no expert on the programming side but I would have thought that your experience of the problems would be a contra-indiction for re-installing the OS.

Firstly Logos would really have had to mess up if running their program actually corrupted the OS. If on the other hand, as one user eventually admitted he had, you have been tweaking the OS personally then putting it back to standard may help.

Your success at running the program with internet disconnected would indicate that the problem lies with either the syncing mechanism or the material that is being synced. Highlighting data, layouts and other items available on the PC side but not implemented yet on the Mac have been shown to cause problems during this consolidation phase.

I would wager, if I were a betting man, that reinstalling the OS might give you something to do, but will make no difference in the long run. Reinstalling the OS is just so Windows and just so not Mac.

But then again I stand to be corrected either by your experience or the knowledge of the Devs.

tootle pip

Mike

Mike S.

https://community.logos.com/discussion/comment/132705#Comment_132705

re-installing the OS

You misunderstood me; I said "on OS X" not "of OS X". I have zero intention of re-installing OS X no matter how unusable L4M gets.

That said, thanks for caring!

Mike S.

https://community.logos.com/discussion/comment/132603#Comment_132603

This should clear up your sync issues after a full re-sync of your data.

L4M crashed early this morning at 3am while attempting to just let it run (trust me, I was doing nothing but sleeping). OS X has a spin log (basically a stack trace, not likely very useful, but could be helpful) and content from the console log I've also attached with the Logos4.log and Indexer.log.

5658.l4mcrashingnow.zip

Michael Hatcher

https://community.logos.com/discussion/comment/132603#Comment_132603

Tom,

I am not Mike S, but since it appeared we had the same problem, I tried deleting the 2 folders and restarted. It seems to have worked for me (at least for now). Thanks for the fix.

Mike S.

https://community.logos.com/discussion/comment/132170#Comment_132170

For those who may run into the same issue, or those that are just curious, the fix was to open the resources that were getting an "FAILED" update in the log with internet turned off, then scroll them, close them and enable internet and sync up.

A HUGE thank you goes out to Tommy Ball and Tom Philpot for their help in getting me taken care of!

Quick Links

Recent Posts
Activity
Unanswered