It seems more times than not Logos 5 is crashing when using the Community Post tool that links to Faithlife forums. Has anyone had this problem or does anyone know what may be the cause of this. When it crashes, it completely shuts down.
Jeff Chappell:Has anyone had this problem or does anyone know what may be the cause of this. When it crashes, it completely shuts down.
What version of Logos or you running? The most recent beta fixes a crash-inducing error in the previous beta that came up in connection with many activities.
Can you post the logs Logos leaves on your system when crashing or better: start Logos with the Ctrl key pressed, thus inducing diagniostic logging, and run it until it crashes, then save the file logos.log before restarting Logos and upload the files here (use the paperclip icon).
Running Logos 7 latest (beta) version
Logos 5 version 5.0a SR-4 is my current version. I will restart Logos as you said and try to duplicate problem, Thanks.
How do I find the logos.log file on MAC?
Jeff Chappell:How do I find the logos.log file on MAC?
To enable logging, press and hold the command key immediately upon startup. This will enable logging for one session. Allow Logos to crash and then grab the log BEFORE you restart Logos.
If you are running 10.7 or 10.8, your user library will be hidden by default. In the finder "go" menu, press and hold the "option" key. This will reveal your user library. The path is Application Support / Logos4/ Logging
OSX & iOS | Mac Logs | PC Logs | Install
Program Version: 5.0a SR-3 (5.0.1.0278)
Mac OS Version: 10.7.5
Processor count: 4
Time: 2013-01-15 11:16:55 -05:00 (2013-01-15T16:16:55Z)
Installed memory: 4,096 MB
Install path: /Applications/Logos.app/Contents/MacOS/lib/LDLS4.Macintosh.dll
Free install space: 816,293 MB
Data path: /Users/jeffreychappell/Library/Application Support/Logos4/Data/78h7n9cf.62x
Free disk space: 816,293 MB
Temp path: /var/folders/p8/6x21_j4n6_qdpfn2ftfs2ybh0000gn/T/
Free temp space: 816,293 MB
Swap usage: total = 128.00M used = 20.81M free = 107.19M
Error ID: 1746
Error detail: TargetInvocationException: Exception has been thrown by the target of an invocation.
System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> Libronix.Utility.Threading.AsyncWorkException: Unhandled exception in asynchronous work. ---> System.IO.IOException: Too many open files
at Libronix.Utility.Threading.AsyncWorkItem.Verify () [0x00000] in <filename unknown>:0
at LDLS4.Panels.CollapsableDataSection+<DoStartWork>c__Iterator35.MoveNext () [0x00000] in <filename unknown>:0
at Libronix.Utility.Threading.AsyncWorkerTask`1[Libronix.Utility.VoidType].EnumMoveNext () [0x00000] in <filename unknown>:0
at Libronix.Utility.Threading.AsyncWorkerTask`1[Libronix.Utility.VoidType].EnumMoveNextWithCatch () [0x00000] in <filename unknown>:0
--- End of inner exception stack trace ---
at Libronix.Utility.Windows.Threading.DispatcherAsyncWorker+<Start>c__AnonStoreyE+<Start>c__AnonStoreyF.<>m__1C () [0x00000] in <filename unknown>:0
at Libronix.Utility.Windows.DispatcherUtility+<BeginInvoke>c__AnonStoreyA.<>m__16 (System.Object ) [0x00000] in <filename unknown>:0
at (wrapper managed-to-native) System.Reflection.MonoMethod:InternalInvoke (System.Reflection.MonoMethod,object,object,System.Exception&)
at System.Reflection.MonoMethod.Invoke (System.Object obj, BindingFlags invokeAttr, System.Reflection.Binder binder, System.Object parameters, System.Globalization.CultureInfo culture) [0x00000] in <filename unknown>:0
at System.Reflection.MonoMethod.Invoke (object,System.Reflection.BindingFlags,System.Reflection.Binder,object,System.Globalization.CultureInfo) <0x0019b>
at System.Reflection.MethodBase.Invoke (object,object) <0x00022>
at System.Delegate.DynamicInvokeImpl (object) <0x00213>
at System.MulticastDelegate.DynamicInvokeImpl (object) <0x00033>
at System.Delegate.DynamicInvoke (object) <0x00016>
at System.Windows.Threading.DispatcherOperation.InvokeOperation () <0x0003b>
at System.Windows.Threading.Dispatcher.InvokeQueuedDispatcherOperations () <0x0010f>
at (wrapper native-to-managed) System.Windows.Threading.Dispatcher.InvokeQueuedDispatcherOperations () <0x00057>
at System.Net.HttpWebRequest.GetRequestStream () [0x00000] in <filename unknown>:0
at Libronix.Utility.Net.WebServiceRequestBase`1[System.Xml.Linq.XElement].WriteRequestContentSync (System.Net.HttpWebRequest webRequest, IWorkState state) [0x00000] in <filename unknown>:0
Program Version: 5.0a SR-4 (5.0.1.0291)
Time: 2013-01-16 08:56:24 -05:00 (2013-01-16T13:56:24Z)
Error handling response (GET https://notesapi.logos.com/v1/popularhighlights/exist?resourceId=LLS%3A1.0.351&resourceVersion=2012-09-26T00%3A29%3A57Z).
System.Net.WebException: The request timed out
at System.Net.HttpWebRequest.EndGetResponse (IAsyncResult asyncResult) [0x00000] in <filename unknown>:0
at System.Net.HttpWebRequest.GetResponse () [0x00000] in <filename unknown>:0
at Libronix.Utility.Net.HttpWebRequestUtility.DoGetHttpResponse (System.Func`1 fnGetResponse) [0x00000] in <filename unknown>:0
Time: 2013-01-16 08:56:25 -05:00 (2013-01-16T13:56:25Z)
Error handling response (GET https://notesapi.logos.com/v1/popularhighlights/exist?resourceId=LLS%3A1.0.171&resourceVersion=2012-10-12T21%3A52%3A27Z).
I'd be glad to look into this problem with you. I notice you've posted some of the callstacks, but a full log (Logos.log) would be helpful. These aren't generated by default and will need to be enabled, following the instructions here: http://www.logos.com/support/logos5/windows/logging.
You can attach them to a reply post in this thread by clicking the paperclip icon when replying. Included a step-by-step description of what you did to create the crash would also be very helpful. Hopefully we'll be able to get to the bottom of this for you very quickly.
Faithlife Tech SupportWin Logs|Mac Logs|Training
Mike, thank you for your response. Attached is the file you requested, i hope i did it right, if not let me know. the crash has occurred several times, form within several layouts. Here is what I do..
Open Logos 5
Goto any layout, open it, let it load
Close the layout by selecting another layout that has already been created.
Select daily reading plan.
Highlight text for community post
right click and select "community post"
that blows me out of Logos...
I do not know if it matters, but i am also unable to share notes docs on faith life. the document appears but cannot be opened or observed by anyone.
It looks like you're experiencing the "too many open files" bug. When we upgraded to Logos 5, we implemented some new features in MONO that allow us to process more data, more quickly. So quickly in fact, that we're hitting a memory cap:
Error: "Unhandled exception in asynchronous work. ---> System.IO.IOException: Too many open files"
Logos 4 wasn't able to multitask the same way, so we didn't experience this problem there. The interface just locked up while it was thinking and forced us to wait for the current process to finish.
Bradley mentioned in another post, that we've developed a fix for this issue in 5.0b (still being developed). Hopefully that will provide a long-term solution for you. Meanwhile, we can avoid this problem by doing less at once. If there's a search running, it may be best to avoid scrolling through heavily marked up resources, or avoid community notes, etc.
This should only be temporary, until 5.0b is released.
I'll look into the faithlife/sharing files issue you're experiencing. That sounds like a separate issue. What types of documents were you sharing? Community Notes, Regular Notes, or anything else?
Sharing notes, and prayer list. the docs show up in documents.logos.com, and are marked "public" either through collaborative or publish actions. they appear greyed out in the faith life.com under documents and are not accessible although it does say "connected" which is also greyed out. You can access the forum at Word of Life Small Group Leaders (faithlife.com) or I can send you an invite if you need. You may also hook up with my computer if you want to. Please let me know if you need any additional info. Thanks and God bless.
Hey Mike, have you had the opportunity to check into sharing notes on faith life. It seems that faithlife is not seeing the shared document content or something...it says connected but there is nothing but a title? Any thoughts?
My apologies for the delay. I'm looking into this with our Faithlife team currently. My understanding is that anyone in a group with shared notes should have access to those notes in Logos 4 or 5. This is different from sharing a Word Document or other file, because these are specifically Logos Notes.
I will reply again as soon as I have a full handle on this feature.