Logos 8.7 crashes when closing out Layouts

✭✭✭

Did I pose that difficult a question? I thought on here, someone could read the log files and see where the problem is, if any at all.

I had nine layouts, three initially when opened & then closed, would crash Logos. Six would not. Has any seen this happen before?

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

I’ve just looked at the Logos.log file and see it is from May

Please ensure diagnostic logging is enabled and upload new logs after a crash

✭✭✭

Thanks for the reply. I've enabled 'diagnostic logging' then opened a Layout. Closing that, it crashed Logos. But when I go to the Directory where the Log Files are, nothing had changed as to the date. I therefore deleted those and repeated and no log files are being created. What am I doing wrong?

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

In Logos 8.5, the log file location was changed!

The release notes - https://wiki.logos.com/Logos_8.5 - have:

Logging

Moved the default logging folder location to:

%LocalAppData%\Faithlife\Logs\Logos\
%LocalAppData%\Faithlife\Logs\Verbum\

Try seeing if more recent logs are there

✭✭✭

Sorry Graham. I cannot find neither of the two which you gave me. Not sure what's going on here unless you've got something else up your sleeve.

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

What happens if you paste “%LocalAppData%\Faithlife\Logs\Logos\” into the locator bar in Windows Explorer?

Do you get to a folder? If so, does it contain any files?

✭✭✭

I'm getting nothing to match. This is getting weirder Graham. The log files I deleted to the Recycle bin now show updated to today's dates. When I restore them, they show the old dates. And of course, I cannot retrieve them from here.

I'm going to give it up for tonight but if you have something else, let it come this way. Thanks for your efforts.

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

✭✭✭

Sorry Graham but I failed to tell you last night that Logos came aboard and took the Log files. I checked in my Sent Box and was able to grab these from there.

As said, this just continues to get more weird as it goes. I followed the path where they took them from and it was on my C: drive whereas Logos is installed on the F: drive.

Still, following the path from where they took the Logs, everything there is completely out of date, no later than 2014. The only thing I can figure out, these are there because in those days, I had Logos installed on the C: drive. But my question is, why when I click on the Properties of these Logs I'm sending to you, have a correct date on them. Anyway, the gal I talked to yesterday said she was going to forward them to the Tech department but I thought maybe someone on here (yourself) could give me an idea as to what's going on.

8231.cef.log

6765.LogosError.log

2146.LogosIndexer.log

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

If I paste the string I posted above into Windows Explorer I get this:

Please post a screenshot showing what you get when you do the same thing.

✭✭✭

Here's what I get Graham .. do you want me to upload these logs again to you?

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

Please upload the logos.log file from that directory

✭✭✭

5468.LogosError-2.log

4454.LogosIndexer.log

4431.LogosSetup.log

MSI Pulse GL76-12UGK Intel Core i7-12700H, RTX3070, 16GB RAM, 1TB SSD, Windows 11 Home

Dave Hooton

The crash log is not very revealing, and the Logos.log was made after the crash, so it is not useful.

We could chase the matter of logs further, but I think it is better to rebuild the layouts that crash.

Dave
===

Windows 11 & Android 13

✭✭✭