3 Crashes a Day

With the latest upgrade to 8.5.0.0026, I am now averaging 3 crashes per Logos session.

The notes are incredibly slow in updating...if they update at all.

I am running Mac OS 10.14.5.

While I am grateful for some of the improvements made with Notes, the constant crashing is something that I don't think was designed.

Is it just me?

Find more posts tagged with

Desktop App

Comments

Jack Caviness

That is not the normal experience of many users. Before anyone can offer assistance, you will need to post logs. See Logos Logs in my signature.

Graham Criddle

https://community.logos.com/discussion/comment/1052482#Comment_1052482

Hi Jack

See Logos Logs in my signature.

It looks as though there is a problem with that destination - it doesn't seem to end up anywhere useful anymore!

Levi Durfey

https://community.logos.com/discussion/comment/1052499#Comment_1052499

Hi Jack

See Logos Logs in my signature.

It looks as though there is a problem with that destination - it doesn't seem to end up anywhere useful anymore!

FL changed the support page a few weeks ago. See here for the new page: https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files

Jack Caviness

https://community.logos.com/discussion/comment/1052500#Comment_1052500

FL changed the support page a few weeks ago. See here for the new page: https://support.logos.com/hc/en-us/articles/360027869132-How-to-Enable-and-Submit-Log-Files

Thought I had linked that page. O' well, we'll try again

greypilgrim

This just started today. It is very frustrating.

LogosError-2.log

greypilgrim

https://community.logos.com/discussion/comment/1053559#Comment_1053559

Here is another log file

LogosError.log

Mark Barnes

https://community.logos.com/discussion/comment/1053559#Comment_1053559

This just started today. It is very frustrating.

There's nothing in the logs that indicates a crash (and indeed, nothing from today). The logs only show a lot of internet connection problems.

Sometimes Logos crashes before it can write a log file. Use the following page to help us diagnose these crashes: How to use event viewer to diagnose Logos crashes

greypilgrim

https://community.logos.com/discussion/comment/1053563#Comment_1053563

-	System

-	Provider

[ Name]

.NET Runtime

EventID

1025

[ Qualifiers]

Level

Task

Keywords

0x80000000000000

-	TimeCreated

[ SystemTime]

2019-06-20T14:11:56.478966200Z

EventRecordID

5726

Channel

Application

Computer

JohnsCloset

Security

-	EventData

Application: Logos.exe Framework Version: v4.0.30319 Description: The application requested process termination through System.Environment.FailFast(string message). Message: Unhandled exception in async work Stack: at System.Environment.FailFast(System.String, System.Exception) at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext() at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object) at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object) at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

Mark Barnes

https://community.logos.com/discussion/comment/1053654#Comment_1053654

Unfortunately, that information doesn't help much [:(]. Is there a pattern to what triggers the crashes? It may need a Faithlife tech to shed some more light on it. For their sake, here's the error log in an easier to read format:

Application: Logos.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception in async work
Stack:
 at System.Environment.FailFast(System.String, System.Exception)
 at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].EnumMoveNext() 
 at Libronix.Utility.Threading.AsyncWorkerTask`1[[System.__Canon, mscorlib, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089]].ContinueExecution(System.Object) 
 at Libronix.Utility.Threading.GroupedThreadPool.ExecuteNextCallback(System.Object) 
 at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) 
 at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean) 
 at System.Threading.QueueUserWorkItemCallback.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem() at System.Threading.ThreadPoolWorkQueue.Dispatch()

Joe McCune (Faithlife)

https://community.logos.com/discussion/comment/1053559#Comment_1053559

This just started today. It is very frustrating.

greypilgrim, it sounds like you are having an unusual problem. I am sending you an email.