BUG: FaithLife Study Bible causes sync freeze

Macbook Pro, OSX 10.8.4, 8 GB RAM, Logos 5.1a Release Candidate (5.1.1.0589)
Ok, I think I've tracked down what is causing it. Someone said earlier (alabama24) that the FaithLife api was having trouble connecting (according to my logs). I removed that resource from the layout (FaithLife Study Bible), removed all layouts that had that resource in it, and restarted (having to force close, of course). After reboot, it synced right up. I pressed sync several times and it synced like a champ. Closed the program, no problem. Closed beautifully. So, just for kicks, I added the FaithLife Study Bible again and, BINGO, sync froze up again. Had to force close. Repeated earlier steps to remove the FaithLife Study Bible and now it syncs without a problem... so far, so good. I'll keep an eye on it and see if it happens again, but so far, I have NOT experienced a freeze during sync. All this time the program did NOT freeze (meaning I could still use it), just the sync portion and it maxed out my fans until I force closed the program (the program would close but then I would have to force close it to get it to close completely). Hope all this makes sense. Thanks so much!
Logs Posted in another thread: http://community.logos.com/forums/t/74170.aspx
Comments
-
Josh Edwards said:
Hope all this makes sense
Makes perfect sense to me. Thank you for your persistence in tracking this. Now, we just need Logos to acknowledge the problem and determine the cause of the freeze.
Unfortunately, I am not completely sure that this is the only cause of all the reported freezes.
0 -
Scratch that... now it's freezing again! Attached are the logs and samples. This is crazy.
0 -
Josh Edwards said:
Scratch that... now it's freezing again!
Learned some words in the US Navy about such situations, but God will not allow me to use then anymore [:D]. Always hated those intermittent and unexplained errors.
Have not been able to cause L5 to freeze for several days now. None of the formerly reliable methods even cause a hiccup. Would be elated, but this does not get us any nearer to solving the problem.
0 -
I have passed along your logs to Development.
0