Passage Lists Cause Logos 4.0d to Crash
I am finding that in either opening or closing a passage list in Logos 4.0d the program crashes. Any suggestions?
Comments
-
Hi Bill
Any more context - what verses are in the passage list?
Or is for all your passage lists?
I can do it without any problem on my system so trying to understand the specifics
Graham
0 -
Bill, we need to see some Diagnostic Logs. Upload the logs Uploading Logs immediately after the crash.
Dave
===Windows 11 & Android 13
0 -
Dave,
I actually rebuilt my entire index but it still does not seem to have solved this problem. I have attached the log files. Thanks for any help you may give.
0 -
What you were doing prior to the crash eg opening an existing PL? Using it in a search? It seems to have crashed after several uses? If you can remember the PL try deleting it in the File menu.
Dave
===Windows 11 & Android 13
0 -
The answer, Dave, is that I just imported my verse lists [some from L2] over to L4 and was clicking on some of them. But, even now, after rebuiding my index I notice that L4 is crashing some. [For example, I tried about 3 morpholotgical searches on a certain word in 2 Peter and it crashed three times. Then, on the fourth, it finally succeeded. However, I had not enabled logging for you to observe this.]
0 -
Dave, here are some logs of a number of crashes I have had in just a few minutes today. They seem to be related primarily to searches and closes of searches. . 8765.Logos Log Files.zip
0 -
Bill, I will look at the logs. If you can upload an image of one or two that are crashing that might also help. But I suspect the answer will be to recreate the ones that are crashing and delete the originals.
Dave
===Windows 11 & Android 13
0 -
Dave,
I have attached some recent log files in which three times in a row L4 crashed for simple searches. [I don't believe it is passage lists causing the problem.]. In this case I was searching in Romans 8:2 for a morphological search of ἠλευθέρωσέν. Thanks for any help you can give.
0 -
BillFiess said:
In this case I was searching in Romans 8:2 for a morphological search of ἠλευθέρωσέν. Thanks for any help you can give.
I will have to leave this for the developers on Monday - I have created a crash record to draw their attention to this thread.
Dave
===Windows 11 & Android 13
0 -
I'm too am having trouble with Logos 4.0d crashing, many times just after it opens. Log file attached. Any suggestions would be appreciated.
John
0 -
Hi John
Please upload the logos4.log for the crash (see my first post).
Dave
===Windows 11 & Android 13
0 -
Dave,
For whatever value it may be, I have included a log of the number of crashes I have had today [Sunday, July 4th]. It's possible that my program is crashing to celebrate the holiday.
0 -
Bill,
Can you try deleting C:\Users\Bill\AppData\Local\Logos4\Data\hzjqnchf.1qw\LibraryCatalog\catalog.db?
It's a bit of a long shot, but it might work. The file will be recreated next time you load Logos (you'll get a "Preparing your library" message).
Mark
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Mark,
I don't have a catalog.db file extension [though I do have some other extensions under catalog]. I believe this problem may have started when I chose to IMPORT ALL after installing Logos 4.0d. Before this, I had not had that much trouble with crashes. It appears [to me, at least] that I have some corrupt files at work. I'm not really sure. I have also attached my most recent log files [if that may help]. Thanks for the assistance you are giving.
0 -
Bill,
Sometimes the .db file extension can be hidden. The file in question will be called 'catalog' and it should be the largest file in that folder (probably at least 10Mb - more depending on the number of resources you have).
Mark
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Thanks, Mark. I praise the LORD that it worked!
Bill
0 -
Mark,
I am [unfortunately] still having a lot of trouble with Logos 4.0d crashing. [See attached log files.] It seems to be mainly on searches. For example, I tried numerous searches on some words [like work or reward] in Rev 22:12 by clicking on the lemma and then SEARCH THIS RESOURCE and the program would crash.
Bill
0 -
Mark,
It looks like I can no longer search with Logos 4.0d. [Almost every search of any time ends with the program crashing.] Do you feel that I should re-install Logos 4?
0 -
The most recent error message for your indexer indicates there was a recent problem with your hard drive.
I would suggesting scanning your disk for errors. To do so, right-click on the drive in My Computer and choose Properties. Then click on the Tools tab and click Check now. Make sure both options are ticked and click Start. The checking will take some time, so perhaps run it over night.
Running the error check will ensure that the bad sectors on your disk won't get used in the future by Logos or any other program. But it won't necessarily fix the existing file corruption that may be there. I would therefore suggest rebuilding your index after you've run the error check. To do so, type rebuild index in the Logos command bar.
This is my personal Faithlife account. On 1 March 2022, I started working for Faithlife, and have a new 'official' user account. Posts on this account shouldn't be taken as official Faithlife views!
0 -
Hi Bill and John,
The crash message you're seeing in the logs is one that's been submitted from a couple of computers, but that we've never been able to reproduce. (And in the other cases it's been reported, I think it's only happened once and then stopped happening when Logos 4 was restarted.) Since you're able to reproduce it frequently, it would be very helpful for us if you could carry out a short diagnostic process for us to collect some more detailed debugging information. Assuming this reports enough information for us to find and fix the bug, we should have a fix available in 4.0d SR-1.
Please follow the instructions at http://wiki.logos.com/Creating_a_Crash_Dump_with_ProcDump to create a crash dump, and send that to me. Since it's likely to be a fairly large file, you can use https://www.transferbigfiles.com/ to send it to my email address (bgrainger at Logos).
Thanks,
Bradley0 -
Thanks, Bradley, for your help. I followed Mark"s [Barnes] advice and checked out my computer for bad sectors [though I don't believe it had any] and now am re-indexing. So I guess I'll have to wait until tomorrow to follow your instructions. [By the way, it was still crashing AFTER I scanned my disk for errors.]
Bill
0 -
Bradley,
After [last night] rebuidling my index, things seem to be running VERY SMOOTHLY. [No crashes this morning at all.] I believe things are fixed with the program. thanks for your concern.
Bill
0 -
BillFiess said:
It looks like I can no longer search with Logos 4.0d. [Almost every search of any time ends with the program crashing.] Do you feel that I should re-install Logos 4?
Bill ~ If you can part with your Passage List documents, please try deleting each of them from the File | Open menu, then retry a search. If that works, recreate one of the lists and run another search. ~ Thanks, Melissa
Sorry, I hadn't read the posts on the second page before replying.
0 -
Bradley,
I started ProcDump using your instructions and will wait for a crash. Mine occurs for no apparent reason, sometimes at startup, sometimes during use. Will e-mail you the .dmp file & either Logos4Crash.txt or Logos4IndexerCrash.txt when I catch a crash.
When a crash does occur, one of these two files in the username\Logos Log Files folder is updated depending upon which program crashed (either Logos4Crash.txt or Logos4IndexerCrash.txt). However, the file "Logos4.log" does not update. The "date modified" remains May 14 7:17pm. Is this what it's supposed to do or should I turn something on to update it also?
John
0 -
Hi Bill & John,
I checked the Windows Error Reporting site today and found a report (that you or some other user has submitted) for what appears to me to be the exact same error. Windows has already collected the debugging information we will need from the system that reported the error to Microsoft, so you don't have to worry about collecting the dump file anymore. Thanks for your willingness to help, though!
I've only been looking at the crash report collected by Microsoft for a few minutes, but it looks like it should have enough information for us to fix the crash in 4.0d SR-1.
Thanks,
Bradley0 -
JohnWerner said:
When a crash does occur, one of these two files in the username\Logos Log Files folder is updated depending upon which program crashed (either Logos4Crash.txt or Logos4IndexerCrash.txt). However, the file "Logos4.log" does not update. The "date modified" remains May 14 7:17pm. Is this what it's supposed to do or should I turn something on to update it also?
Logos4Crash.txt is always updated whenever the program crashes. Logos4.log is only modified when logging is enabled (see http://wiki.logos.com/Diagnostic_Logging). There's no need to turn the logging on since it slows the system down a little (and also doesn't provide useful information for this specific problem).
0 -
Bradley Grainger said:
I've only been looking at the crash report collected by Microsoft for a few minutes, but it looks like it should have enough information for us to fix the crash in 4.0d SR-1.
That is good, I was worried this might go on a bit longer.
Dave
===Windows 11 & Android 13
0
