Crash: SR7: Hang on start-up

I had been running Logos for a long time and had lots of tabs open.
I switched to Firefox and ordered the "12 Days" special of the day.
After completing my purchase, I closed Logos.
I attempted to start Logos back up again and it hung forever at the splash screen. No Logos icon in the tray.
I checked out what it was doing in Process Explorer, but it was completely inactive.
Eventually I had to kill the process. Log files here: 4062.Logos4Log.zip

UPDATE: I looked again at the log files after having killed the process and apparently it was still doing something, as a few more lines had been added. But there was absolutly NO visual feedback to me that anything was still being downloaded and for all practical purposes, even to this techie, it looked like the program had hung. Here are the updated log files: 0724.Logos4Log.zip

I just tried to boot it again and it's hung again. I'm going to leave it overnight and see what happens.

Find more posts tagged with

Comments

Rosie Perera

Another update: The SyncManager is still putting out two new lines in the end of the log file every five minutes or so. Still no visual feedback to me that anything is happening, but my hard disk light is flickering like crazy. No new resource files are showing up in my resource folder.

Here's what I get from Process Explorer:

Of interest is that the State of the main logos.exe thread is "Wait:DelayExecution". I'm not sure what that means but it seems to point to something hung up that shouldn't be. The states of all the other threads are as follows:

11936 - Wait:UserRequest
10540 - Wait:UserRequest
11080 - Wait:UserRequest
184 - Wait:WrQueue
10656 - Wait:UserRequest
6268 - Wait:WrQueue
5480 - Wait:WrQueue

Hmmm....are some of these threads waiting for user input from me??? It sure isn't showing me anything I'm supposed to respond to.

OK, I'm going to shutdown my whole computer and restart and see what happens. Back soon...

Rosie Perera

https://community.logos.com/discussion/comment/58709#Comment_58709

Wait, stop the presses... I killed that Logos process, and there were two other logos4.exe processes running. I killed them too (unfortunately neglecting to get such detailed info about them as I did above with the first one), and then suddenly the Logos4Indexer.exe started up. It seems to be running fine right now. Blue Logos icon in the tray, says "Logos Bible Software is indexing (0h 2m remaining)" but it's been stuck like that for more than 2 minutes. Oops...now it says "0h 3m remaining)."

OK, it finally finished. I tried to boot Logos. It crashed. ("Logos Bible Software 4 has stopped working.")

Tried again. Ditto. I must have broken it by killing processes that were in process. This time I'm really going to reboot and we'll see...

Rosie Perera

https://community.logos.com/discussion/comment/58713#Comment_58713

OK, I've rebooted. Logos still crashes when I try to start it up, but this time it produces the following Application Error:

When I clicked OK on that, what was left of Logos shut down and the Indexer started up again automatically.

Log files from the last few crashes (including this most recent one last, named Logos4-7.log) look innocuous to me, but I'm attaching them all here:
7242.Logos4Log-7418c.zip

Is there some file I can delete to get beyond this crashing problem? I am completely dead in the water, unable to run Logos. It really pains me to add to the suspicions of newbies reading this forum. [:(]

AndyTheGreek

https://community.logos.com/discussion/comment/58720#Comment_58720

If you have a backup of a previously working instakllation, this would probably be the time to try restoring it.

I suspect that some of these problems are due to database/index files getting corrupted. But that's just a guess.

Andy

Mark Barnes

https://community.logos.com/discussion/comment/58720#Comment_58720

I presume you've tried holding down CTRL and logging in with a blank workspace?

Rosie Perera

https://community.logos.com/discussion/comment/58750#Comment_58750

I presume you've tried holding down CTRL and logging in with a blank workspace?

No, I hadn't. I didn't know you could do that. That worked. There's still a bug somewhere that allowed me to get into that state, though. Hopefully the logs will help Logos figure it out, but I have no idea what I was doing before I shut down the first time, so I probably can't describe a reproducible case.

I'll log it over on the wiki and see what they think.

Mark Barnes

https://community.logos.com/discussion/comment/58752#Comment_58752

It's a discussion for another thread, but this is exactly the sort of thing that should be in the Wiki FAQ, I think. This solves about 90% of "I can't load Logos at all" problems, and if you didn't know about it....

Rosie Perera

https://community.logos.com/discussion/comment/58755#Comment_58755

It's a discussion for another thread, but this is exactly the sort of thing that should be in the Wiki FAQ, I think. This solves about 90% of "I can't load Logos at all" problems, and if you didn't know about it....

I knew there was something about holding down Ctrl when starting up would enable logging, but I'd never tried that, because I instead ran the script that enables logging all the time. I've always been mystified when people talk about logging in, because I had only once ever seen that login screen, when I first installed L4 during beta. Now I know!

Yes, indeed, this belongs in the wiki! I'm seriously going to bed now, though...

TCBlack

https://community.logos.com/discussion/comment/58759#Comment_58759

I knew there was something about holding down Ctrl when starting up would enable logging, but I'd never tried that, because I instead ran the script that enables logging all the time. I've always been mystified when people talk about logging in, because I had only once ever seen that login screen, when I first installed L4 during beta. Now I know!

Yes, indeed, this belongs in the wiki! I'm seriously going to bed now, though...

It is there: Diagnostic Logging

Mark Barnes

https://community.logos.com/discussion/comment/58842#Comment_58842

It is there: Diagnostic Logging

It isn't. That just tells you how to turn logging on. It doesn't tell you that holding CTRL also allows you to start with a blank layout.

TCBlack

https://community.logos.com/discussion/comment/58855#Comment_58855

It is there: Diagnostic Logging

It isn't. That just tells you how to turn logging on. It doesn't tell you that holding CTRL also allows you to start with a blank layout.

It does now. [;)]

Melissa Snyder

https://community.logos.com/discussion/comment/58720#Comment_58720

Log files from the last few crashes (including this most recent one last, named Logos4-7.log) look innocuous to me, but I'm attaching them all here:
7242.Logos4Log-7418c.zip

Rosie,

Thanks for the logs; we'll take a look at them.

Update: Apparently an updated file built for 4.0a, and not compatible with 4.0, was mistakenly published (and promptly pulled) yesterday. This caused a problem for users who got the file before it was pulled. Updating to 4.0a when it's released will resolve the problem.

Melissa

Rosie Perera

https://community.logos.com/discussion/comment/58903#Comment_58903

Log files from the last few crashes (including this most recent one last, named Logos4-7.log) look innocuous to me, but I'm attaching them all here:
7242.Logos4Log-7418c.zip

Rosie,

Thanks for the logs; we'll take a look at them.

Update: Apparently an updated file built for 4.0a, and not compatible with 4.0, was mistakenly published (and promptly pulled) yesterday. This caused a problem for users who got the file before it was pulled. Updating to 4.0a when it's released will resolve the problem.

Melissa

Thanks, Melissa. Which file was it? In the meantime I'd like to avoid opening that resource.

Rich DeRuiter

https://community.logos.com/discussion/comment/59023#Comment_59023

Thanks, Melissa. Which file was it? In the meantime I'd like to avoid opening that resource.

At least one problem file is the Logos Help file. Searching the updated help file in SR-7 causes Logos4 to crash. This wouldn't explain your crash though, since you were not likely running a search on the help file on loading Logos4 (or was a search on help active when you shut-down?)

I'm unaware of another file causing issues. If there is, I'll be watching for it.

Melissa Snyder

https://community.logos.com/discussion/comment/59023#Comment_59023

Thanks, Melissa. Which file was it? In the meantime I'd like to avoid opening that resource.

We've been told that there isn't a simple workaround, such as deleting a file, besides opening to a blank layout, as you have been doing.

Melissa

Rosie Perera

https://community.logos.com/discussion/comment/59029#Comment_59029

Thanks, Melissa. Which file was it? In the meantime I'd like to avoid opening that resource.

At least one problem file is the Logos Help file. Searching the updated help file SR-7 causes Logos to crash. This wouldn't explain your crash though, since you were not likely running a search on the help file on loading Logos4 (or was a search on help active when you shut-down?)

I'm unaware of another file causing issues. If there is, I'll be watching for it.

It could have been that Help was active when I shut down. I see now that searching it does cause a crash. Bummer. I used Help a lot. Will just have to hang on for 4.0a.

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/58709#Comment_58709

Of interest is that the State of the main logos.exe thread is "Wait:DelayExecution". I'm not sure what that means but it seems to point to something hung up that shouldn't be.

My best guess (from the log file) is that Logos4.exe has instructed Logos4Indexer.exe to shut down so that it can install new licenses. It's waiting for the process but apparently the event isn't getting signalled.

I haven't seen this exact situation before (so it's probably a rare timing issue?), but I already fixed a similar bug in 4.0a; that might also solve this problem.