Bug: Crashing while reading LEB

Lynden O. Williams

Logos had just finished John 17 and moving into chapter 18 when it suddenly crashed. The Bible was the only one opened.

I had minimized it to open another program Outlook 2013.

3073.LogosError.log

87115.Logos.log

The crash log has an October date. These are the only two with todays date.

Find more posts tagged with

Comments

Lynden O. Williams

Left it reading and switched to the browser after a restart. Now it is echoing in John 21.8037.awesomium.log

This error was recorded after bringing the computer out of sleep this morinig. Logos was not runing at the time.

Bradley Grainger (Logos)

I didn't see any crashes in the log files. Are there details on the crashes in Event Viewer?

Lynden O. Williams

Thanks Bradley. Where should I look in the event viewer?

Bradley Grainger (Logos)

Look under Event Viewer (Local) > Windows Logs > Application (in the tree view on the left).

Then, in the main window, look for for an "Error" logged by ".NET Runtime". Select the information and paste it into a reply here.

Lynden O. Williams

Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6F724673
Stack:

Lynden O. Williams

Just as it moved from John to Acts, the echoing started and then crash.

0435.Logos.log

The only one with the right time stamp. Will enable diagnostic logging again. Never changed it.

Lynden O. Williams

Application: Logos.exe
Framework Version: v4.0.30319
Description: The process was terminated due to an unhandled exception.
Exception Info: exception code c0000005, exception address 6D617267
Stack:

Thomas Ball

Hi Lynden,

I think it will be easier to troubleshoot this if you call us at your earliest convenience.

800-875-6467. We're open 6am PST - 6pm PST.

Angela Murashov

This crash should be fixed in 5.2a Beta 5.