BUG: Sync STILL freezing

Josh,

Just to CONFIRM, I have the SAME issue! I HAVE NOT posted but I have to repeatedly do a FORCE QUIT simply because the exit sync continues. After a very short time of using L5 my fan will also begin to run and when I finally get L5 shut down the fan eventually stops so I know it is caused by L5. NO other program causes the fan to run except L5.

Bob

t I'm getting sick of not hearing anything about this issue.

While I understand your frustration with the bug, you are incorrect in your statement that Logos has not responded. There have been a number of posts on this issue in these forums, many from Logos employees. Logos has not been able to reproduce this problem with their computers.

it must be an issue with Logos servers or something.

Not likely the cause, as the freeze only exists with the Mac OS. Are you using a Mac Book, and have you closed the lid with Logos running? I know this should be an allowed action; I'm just trying to identify the circumstances under which the freeze occurs.

I had a number of freezes upon quit earlier with a desktop Mac, but have not been able to reproduce the problem recently. I switched from an older Mac Pro to a 2013 iMac recently. Now, I cannot remember it the freezes stopped for me prior to the switch or after it.

The more information we can give as to our actions prior to the freeze, and the more logs we submit, the more likely that Logos will find the cause—or causes—of these freezes.

Must leave for Church now, but why don't you try updating to 5.1a SR-1?

https://community.logos.com/discussion/comment/523764#Comment_523764

Just to CONFIRM, I have the SAME issue!

How do you know that it is the SAME issue? [:P]

(Same Symptom does not necessarily equal Same Problem)

https://community.logos.com/discussion/comment/523779#Comment_523779

Jack, thanks for pointing out my error. [:P] However, I never saw where Logos said they couldn't reproduce this problem. I'm not saying it doesn't exist, but I also don't read every forum post so it's possible I missed a few of the threads regarding this issue. The only response I've seen from Logos personally is that they would pass the logs on to development.

To answer your question, no I never closed the lid on my computer with Logos open. All I have to do to reproduce the issue is open the program (the initial sync does fine usually) and change something (either highlight, add a note, move a resource to a different pane and bam, the sync goes on forever. Right before this post, it did it again... So, again, here are more logs. Yes, my macbook is a little older (probably 2 years old) but it works fine for everything else. I really want to like Logos. I do... some of my favorite commentaries are on it. This issue is just so frustrating.

Oh, here are the logs again... and I'm posting while Logos HANGS in the background refusing to close because it CAN'T SYNC!

7853.LogosLogs.jedwards1981.20130908-133222.zip

3441.LogosLogs.jedwards1981.20130908-133243.zip

https://community.logos.com/discussion/comment/523841#Comment_523841

Here's another set of logs as Logos chugs away in the background. Computer temp already up to 85 degrees and fans are whirling away. Hope someone can make sense of these. Here's what I did. Opened Logos, changed my scripture, hit sync, it completed fine. Highlighted something in a commentary and hit sync again... boom. Sync froze.

8204.LogosLogs.jedwards1981.20130908-150913.zip

8561.LogosLogs.jedwards1981.20130908-150929.zip

https://community.logos.com/discussion/comment/523861#Comment_523861

8561.LogosLogs.jedwards1981.20130908-150929.zip

This sample contains numerous libsystem errors. Unfortunately, I do not know enough the determine their meaning. Perhaps Bama knows something about them. Otherwise will see if I can get someone with more technical expertise to take a look tomorrow.

8204.LogosLogs.jedwards1981.20130908-150913.zip

Logos.log contains multiple SyncClient errors. Again, will try to get someone with more expertise to take a look.

Also note that you are using Logos 5.1a. You could try updating to 5.1a SR-1. It may not fix the problem, but at least you will be using the latest version of Logos 5.

https://community.logos.com/discussion/comment/523865#Comment_523865

This sample contains numerous libsystem errors. Unfortunately, I do not know enough the determine their meaning. Perhaps Bama knows something about them.

Uhh. Did the teacher just call on me? [:)] (I'm not much help here, sorry).

Also note that you are using Logos 5.1a. You could try updating to 5.1a SR-1. It may not fix the problem, but at least you will be using the latest version of Logos 5.

Yep. I would try updating... I don't think it is the problem, but it should be done anyways and doesn't hurt.

Josh - Would you mind posting a screen shot of your layout when you close? What do you have opened? Do you have any shared documents? Shared Faithlife Notes?

https://community.logos.com/discussion/comment/523873#Comment_523873

Ok, I updated to the SR-1 release (I thought the beta was the latest release). I can't seem to make it freeze now, no matter how hard I'm trying. But I don't think it's completely fixed. Here is a screen shot of my layout. No shared documents or Faithlife stuff open. I did notice something, though. There are several lightly underlined things in my commentaries showing how many other people have highlighted the same section (like in Kindle books). It seems as if when it was syncing, those just "showed up" then the sync would finish. So it may have to do with that. Is it possible to turn that off so it doesn't show when others have highlighted it? I looked through the preferences, but I didn't see an option for it.

https://community.logos.com/discussion/comment/523917#Comment_523917

I updated to the SR-1 release (I thought the beta was the latest release).

If you were on Beta channel, you need to switch to stable to receive service releases. Otherwise, you will have to wait for the next beta release. (SR's are not released through beta channel).

I did notice something, though. There are several lightly underlined things in my commentaries showing how many other people have highlighted the same section (like in Kindle books). It seems as if when it was syncing, those just "showed up" then the sync would finish. So it may have to do with that. Is it possible to turn that off so it doesn't show when others have highlighted it?

Those are "popular highlights." I don't think this is the cause of your problems… and I don't think turning it off will stop the data from syncing… but maybe. To turn them off, access it via the visual filter menu (three intersecting circles). To turn it off for ONE resource, uncheck the box. To disable them for ALL resources, right click on the "popular highlights" in the menu.

https://community.logos.com/discussion/comment/523917#Comment_523917

I can't seem to make it freeze now, no matter how hard I'm trying. But I don't think it's completely fixed.

That is my situation. Previous had freezes, but somewhere along the line they stopped. Now I cannot make it freeze—which is fine except it does not help identify the source of this bug.

https://community.logos.com/discussion/comment/523779#Comment_523779

Bama,

Sorry my choice of words was not to your liking however, the truth is I do not need, nor relish a lesson in semantics! My box is doing the SAME thing! The reason why is beyond my knowledge level.

Bob

https://community.logos.com/discussion/comment/524080#Comment_524080

The reason why is beyond my knowledge level.

Bob - I really wasn't trying to give you a hard time... too much. The point of my post was that the same symptoms do not equal the same disease. If you are having difficulties, it is best to explain them and provide the necessary info so that it can be confirmed or denied to be the "same problem." This is particularly important with an issue like this one since Logos has not been able to replicate the issue... and we know that there is more than one cause for the symptom.

https://community.logos.com/discussion/comment/524111#Comment_524111

The program stays responsive, no problem. It only causes the program to hang when exiting. However, it causes my GPU temp to spike and the fans to mimic the now retired Concorde taking off. This is exactly what is happening and it matches perfectly to what the OP stated.

https://community.logos.com/discussion/comment/524127#Comment_524127

I'll stop bugging you. If you are interested in helping fix the problem, please post logs.

Ok, this is getting just ridiculous! Since it has to do with sync, it must be an issue with Logos servers or something. The program stays responsive, no problem. It only causes the program to hang when exiting. However, it causes my GPU temp to spike and the fans to mimic the now retired Concorde taking off. Attached are my logs, but I'm getting sick of not hearing anything about this issue. I really want to like Logos software and use it, but this item is really getting on my nerves.

I should have a fix for this soon. I apologize for the annoyance of this issue.

Regards,

Seth Copeland

Logos SW Development

https://community.logos.com/discussion/comment/524127#Comment_524127

The program stays responsive, no problem. It only causes the program to hang when exiting. However, it causes my GPU temp to spike and the fans to mimic the now retired Concorde taking off. This is exactly what is happening and it matches perfectly to what the OP stated.

Hi Bob,

Are you running Logos 4, or Logos 5. The latest service release for Logos 4, 4.6c-SR4 (release notes here: http://wiki.logos.com/Logos_4.6c_SR-4) should have a fix for this problem, and a similar release will go into the next service release for Logos 5. If running Logos 4, let me know if this fixes your problem.

Regards,

Seth Copeland

Logos SW Development

https://community.logos.com/discussion/comment/524570#Comment_524570

Seth,

I am running L5 RC4 on Mountain Lion. The longer I allow L5 RC4 to run (especially sit idle) the more likely I am to have this problem! If I open up L5 use it then shut it down it seems to not be as prone to do this.

https://community.logos.com/discussion/comment/524724#Comment_524724

I am running L5 RC4 on Mountain Lion.

Bob

Why not upgrade to 5.1a SR-2? That may very well solve your problem.

https://community.logos.com/discussion/comment/524747#Comment_524747

I am in error. I am actually on L5 5.1a RC4 build 5.1.1.0594

https://community.logos.com/discussion/comment/524803#Comment_524803

I am in error. I am actually on L5 5.1a RC4 build 5.1.1.0594

FYI - When you are on beta channel, you need to switch back to stable to receive service releases. [:)]

https://community.logos.com/discussion/comment/524811#Comment_524811

Thank you Bama. I sincerely appreciate the help.

https://community.logos.com/discussion/comment/524835#Comment_524835

Sure thing. I normally switch back to stable and wait for a couple of builds before moving back to beta. Hopefully that gets the BIG bugs out of the way.

https://community.logos.com/discussion/comment/524803#Comment_524803

I am in error. I am actually on L5 5.1a RC4 build 5.1.1.0594

That is not the latest build. You will need to switch your update channel to Stable in order to get that one. Services Releases are only available on the stable channel. I then switch back to beta channel after the first beta in release in the next upgrade cycle.

https://community.logos.com/discussion/comment/524838#Comment_524838

Didn't know that. Thanks Jack!

https://community.logos.com/discussion/comment/524724#Comment_524724

Seth,

I am running L5 RC4 on Mountain Lion. The longer I allow L5 RC4 to run (especially sit idle) the more likely I am to have this problem! If I open up L5 use it then shut it down it seems to not be as prone to do this.

If you could attach your logs I can look into it more (see the links in alabama's signature area). The main issue of endless sync on shutdown should be resolved with the next stable release on Logos 5 (if you ran logos 4 it was fixed in yesterdays stable release).

Regards,

Seth Copeland

Logos SW Development

https://community.logos.com/discussion/comment/524839#Comment_524839

Okay, I have switched to the stable channel and I am updated to 5.1a SR 1 (5.1.1.0600). Will post any issues encountered. Thanks for the help!

https://community.logos.com/discussion/comment/524844#Comment_524844

The main issue of endless sync on shutdown should be resolved with the next stable release on Logos 5

Wonderful news. Thank You very, very much [Y] [<:o)] [B] (I'm Baptist, so that is root beer [8-|])

https://community.logos.com/discussion/comment/524873#Comment_524873

Okay, I have switched to the stable channel and I am updated to 5.1a SR 1 (5.1.1.0600). Will post any issues encountered. Thanks for the help!

Today's stable release http://community.logos.com/forums/t/75306.aspx should prevent the endless sync on shutdown problem from occurring. (Still could take a minute or two if you have a spotty connection or a lot to sync right at shutdown).

Seth

https://community.logos.com/discussion/comment/526826#Comment_526826

Okay Seth,

I installed and I think all is well. I have L5 running in the background right now and will know for sure if it is fixed real soon! Thanks for the info and the hard work!

https://community.logos.com/discussion/comment/526826#Comment_526826

Today's stable release http://community.logos.com/forums/t/75306.aspx should prevent the endless sync on shutdown problem from occurring.

What about the beta channel? Or is it not a problem there?

I did start a thread concerning a different freeze when opening a layout with a floating Library window FREEZE: 5.1b Beta 1 Mac

https://community.logos.com/discussion/comment/526962#Comment_526962

What about the beta channel? Or is it not a problem there?

Here is my understanding of the process... I could be wrong. [:P]

They added the fix to the SR so that people on stable (the vast majority of users) would have the fix. When it comes to beta, the process of adding new features, etc. means that it isn't always wise to add "new stuff" when you are working on some issues... so a fix like came in the SR might be a little bit down the road for beta users... which is why we get the typical warnings.

I remember once where the "quick fix" release, for whatever reason, ended up being worse than the initial problem. [:S]

https://community.logos.com/discussion/comment/526962#Comment_526962

What about the beta channel? Or is it not a problem there?

I believe the fix is in the most recent beta that was shipped. You should not encounter the endless sync on shutdown any longer.

Regards,

Seth

https://community.logos.com/discussion/comment/527038#Comment_527038

I believe the fix is in the most recent beta that was shipped. You should not encounter the endless sync on shutdown any longer.

Haven't had that one in quite a while, but I did experience a new one in opening the Library window (reported in the Beta forum—Dylan has created a case for it)

https://community.logos.com/discussion/comment/526948#Comment_526948

The endless sync problem is STILL occurring! The only way out of it is to do a force quit! This is occurring on the Mac platform running ML.

https://community.logos.com/discussion/comment/527952#Comment_527952

The endless sync problem is STILL occurring! The only way out of it is to do a force quit! This is occurring on the Mac platform running ML.

How long did you wait before force quitting? Could you attach logs?

Regards,

Seth

https://community.logos.com/discussion/comment/528018#Comment_528018

I waited far more thanwhat has been customary in the past. My guess is 3-5 min.

https://community.logos.com/discussion/comment/528083#Comment_528083

I waited far more thanwhat has been customary in the past. My guess is 3-5 min.

I wonder if this is a different error. I was able to reproduce the endless sync by simulating a bad connection so that web requests failed, and it would be stuck trying to sync. After the fix, when it experiences web connection errors it stops retrying and gives up. However, if you simply have a very slow connection so that it doesn't fail, or takes a long time to do so, it could be that it is actually still trying, and is taking a long time to timeout. There might be something specific on the mac, that makes a timeout take a lot longer to occur. If you post logs, I should be able to investigate further.

Regards,

Seth Copeland

https://community.logos.com/discussion/comment/528086#Comment_528086

Hopefully these logs will help.

0525.LogosLogs.rcdeacon.20130920-133852.zip

https://community.logos.com/discussion/comment/528090#Comment_528090

Hopefully these logs will help.

Bob - I know this has been a hassle for you, but thanks for taking the time to report this issue. I'm not experiencing this issue like you are, so your diligence is <prayerfully> very beneficial to other Mac Logos users. [:)]

https://community.logos.com/discussion/comment/528090#Comment_528090

Hopefully these logs will help.

This is slightly different than the other problem. The other problem was it would retry syncing over and over, in this case, it is that it is only trying once, but the web requests are failing because they are taking too long and timing out. Usually when there is a connection error, it fails way before it timeouts, so I'm not exactly sure what is occurring here.

I can't figure out why in the logs it looks like it is syncing fine, and then all of a sudden all web requests start timing out. I'm assuming this is probably when you requested to close the app, and then since each web request seems to be taking 5 minutes to know that it has failed, it ends up taking a very long time. If you are on wifi, when it hangs if you tried going into airplane mode, I'm curious if it would stop timing out and fail sooner so that it could close.

We'll keep looking into it.

-Seth

https://community.logos.com/discussion/comment/528107#Comment_528107

Although it has been a very LONG time since I have been pleased with Logos (not since L3 days) I continue to hope and continue to alternate back and forth with another product. There are some things about Logos I really love but nagging, annoying problems like these tend to be very frustrating.

What I will do is continue to use L5 and leave it running since the problem in the past seemed to occur when it was left running. This time I will leave it to sync and see if it will ever finish. I am available for any kind of screen share or phone conversations if needed. I will do whatever I can to help fix this!

https://community.logos.com/discussion/comment/528120#Comment_528120

Unfortunately, I can CONFIRM this is still happening. I thought it was fixed. Here are logs and a screenshot of where it sat for 5 minutes. I tried turning off wi-fi when the wheel started spinning, but it never failed and closed. That's why the wi-fi is off in the screenshot below. For some reason it's hanging causing the CPU temp to spike and the fans to ramp up. Anyway, hopefully you can find out what's going on. Hope these help.

3857.LogosLogs.jedwards1981.20130921-075840.zip

1651.LogosLogs.jedwards1981.20130921-075853.zip

https://community.logos.com/discussion/comment/528303#Comment_528303

I experienced, yet again, another freeze during sync and my fans went to full and temps shot up. Here are the logs and a screenshot showing that Logos was using 379.2% of the CPU. I really hope you all are making headway on this.

8637.LogosLogs.jedwards1981.20130927-074111.zip

4062.LogosLogs.jedwards1981.20130927-074118.zip