BUG: Logos fails to open (unless Ctrl held down)

Okay, I've turned on permanent logging. Here's the log file from today's crash.

Same symptoms: Logos still crashes to desktop, unless I hold down Ctrl, sign in, and load a layout. Suggestions?

1030.LogosLogs_AllenBrowne_2023-08-08.zip

I'm no longer an MVP and am leaving today on a 3-week trip, so I don't have time to look into it. Hopefully one of the current MVPs who knows log files better than I do will see this and take a look.

Enjoy the break, Rosie. Sure appreciate what you have done for me and for others over so many years.

I am not a master log reader... I tried to read yours, but nothing was there which I knew how to fix. I saw something about expected downloads which weren't there, and also something about an unexpected link set in the NIV.

However, your situation isn't fully clear, so for clarification: 

• When you try to start the app normally, it crashes (on its own).
• You are able to load to a blank layout.

Are both of those fully true? Have you restarted the computer with the same results? What does Logos normally open to with your settings? (for example, I open to "most recent layout: local".). If you normally open to a layout, have you tried using a different layout? Building a simple one from scratch and opening to it?

Thanks for checking JT.

Yes: both points are true. Logos crashes (disappears from the screen, and is not shown as a runnig app in the Windows Task Manager). But it does start to a blank layout (by holding down Ctrl). I can then I can load any saved layout and it works fine.

This has been happening for several days. I've restarted the PC several times.

Will try the patch Tuesday updates and report back as to whether that helps.

Thanks again.

NOT RESOLVED:  my Logos crashes are back.

Logosd 27.2.21 loads successfully if I set “At Startup Open To: Blank Layout” (under program settings). I can then open my preferred layout, and continue as normal.

If the At Startup Open To is set to “Most recent layout: Local” then I see the splash screen, the synching notification, the main window opens briefly and then disappears. Then I don’t have Logos on screen, and it’s not listed as a running app in the Windows Task Manager.

That may be a hint that the crash has to do with the timing of the attempt to load my layout?

The layout isn't particularly complex (screenshot below, with logs).

The laptop is pretty standard:Dell G7 (17 7790), i7 9750H, 32 GB RAM. 2 x SSDs (Logos is on with 1TB free). All updates for Windows, Intel, and Dell applied (no betas). The crashes occur even with all external devices unplugged (mouse, keyboard, 2nd screen, audio DAC).

Startup list is minimal: drivers for Logitech mouse &keyboard, FiFO audio, Intel graphics, and Microsoft Defender. (Disabled: Terminal, Cortana, Phone Link, and OneNoteM.)

Today's Logs:

7103.LogosLogs_AllenBrowne_2023-08-12.zip

My normal layout looks like this:

When the app crashes as indicated, you must zip and upload the folder of logs before restarting the app.

Thanks, Dave. I'm using EnableLogging.js to toggle logging on/off, and I'm not sure if it's currently on or off.

The only file in the Logs folder that has the current date and time is LogosError.log, so I've attached that.

0724.LogosError.log

Just run (double-click) Enablelogging.js and it will confirm that logging is enabled.

I need a zipped folder of logs after a crash and before you restart (selecting files is not sufficient).

Thanks for your help, and sorry the delay.

When I double-click EnableLogging.js I see a security warning but no report of whether logging is on or off. So I've uploaded the logs twice, running the js in between.

6278.LogosLogs_AllenBrowne_2023-08-15a.zip

7041.LogosLogs_AllenBrowne_2023-08-15b.zip

Both times immediately after running the javascript, Logos opened successfully to a blank screen (even though I've set "At Startup Open to" to "Most recent layout-local." So I closed it and it crashed next time. The logs are from after each crash.

When I double-click EnableLogging.js I see a security warning but no report of whether logging is on or off. ...

And it has not worked for you, so enable logging by starting Logos with CTRL key held. After crashing, upload the logs before you restart.

EDIT:  I got it to run via right-click and Open with Microsoft Windows Based Script Host.

Thank you. Using right-click and open with wscript.exe, I got the dialog saying logging is on. Logs attached.

0755.LogosLogs_AllenBrowne_2023-08-15c.zip

(If I hold down Ctrl, it opens to a blank screen without crashing, so I don't think that would generate a log of a crash.)

This shows a normal exit and not a crash! Are you uploading before you restart Logos?

Trying again:

8585.LogosLogs_AllenBrowne_2023-08-15d.zip

Trying again:

This shows the main window being opened at 7s (probably blank) and then panels being loaded: 2 for NIV 2011 and 1 for ESV Catholic and 2 others. The log finishes 1 second after that. Is that what you mean by "fails to open" in that you started Logos normally (without the CTRL key)?

What I see is the splash window, the synching dialog, then the main screen with a blank layout for maybe half a second. Then the blank Logos window disappears (crash to desktop), and Logos is not running (not listed as running in the Windows Task Manager).

My current workarouns is to set Program Settings | At Startup Open to: "Blank Layout." I can then load a layout, and use Logos as normal, so it's not a desperate problem at present.

Hopefully, Faithlife will enter the discussion.

Thanks, David. I have every hope they will track this down and address it in time.