NEW CRASH: 5.2b beta 5
I had a similar crash here
http://community.logos.com/forums/t/86532.aspx
that was a result of Text Comparison and running "Gen-Rev" from Home Page. This one was attributed to trying to do a lot of work in a bunch of panes that open from the Home Page.
Now, I got a bunch of Sermon resources updated, so I wanted to see what had been added to the Sermons section. So I JUST opened Passage Guide, typed "Gen-Rev", and got this crash. Verbum had only been opened for about 10 minutes. This was just running PG:
Comments
-
To allow this to work, create a custom guide that only has the Sermons section.
The current version of Logos does not support running a full PG on the entire Bible, sorry.
0 -
To allow this to work, create a custom guide that only has the Sermons section.
FYI I Had all the sections closed so the only thing running was sermons.
But your idea does not work either, I created a Guide with only a Sermons section, that too crashes (you can see it partially in the upper left corner):
0 -
I created a Guide with only a Sermons section, that too crashes
This works fine for me. You may want to post logs of just opening Logos and running that new guide.
EDIT: Note though that I'm testing with Logos 5.2b Beta 5.
0 -
I am also on Beta 5, here is the clue - after seeing your post Randy, I went back and tried it - twice with my existing custom passage guide, it ran with no crashes. But then I tried this - I started Verbum, created a custom passage guide, then ran it - it crashes every time so far! You have to start, create a guide, then run Gen-Rev. Here are my logs:
0 -
You have to start, create a guide, then run Gen-Rev.
I've tried these steps, and it worked fine on my machine. I looked at your logs, and it's pretty clear that you're running out of memory:
Error ID: 8037
Error detail: OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown.So, it makes sense that you can open the existing one because the data has been generated. As for why you're running out of memory, do you have a lot of background applications running? It might be good to run Task Manager and monitor the memory usage before and during the running of the Guide.
0 -
I couldn't reproduce this either using Logos.exe with Verbum set to either yes or no. I assume Verbum.exe would be the same?
I didn't think an app would normally run out of memory because of the memory use of other applications except under extreme conditions??? Windows usually manages that pretty well. Most of the time it's internal for 32 bit apps or possibly running out of disk space or other resource. Does it work for smaller ranges? Or can the crash be isolated to a certain range?
EDIT: I note Don's log files show he has plenty of available RAM and disk space. More than my system and I have a hard time maxing it out.
0 -
I have 32GB on this computer, and Verbum does not get above 1 GB in this test. I usually have about 5 GB in use, so plenty of memory is available. That doesn't mean that Verbum is not using up what it needs somehow.
0 -
I've tried these steps, and it worked fine on my machine
Dylan did you try it with Verbum beta or Logos?
0 -
I couldn't reproduce this either using Logos.exe with Verbum set to either yes or no. I assume Verbum.exe would be the same?
Verbum.exe is a totally different executable than running this with Logos.exe and Verbum set to yes. It might be good if someone could try and duplicate this with Verbum.exe. Run it - creat a custom guide with just Sermons - close the template - Run the custom Passage guide for Gen-Rev.
0 -
Dylan did you try it with Verbum beta or Logos?
Verbum Beta 5. Start app, create custom Guide (Sermons only), run on Gen-Rev. No crash, and loaded in ~1 second.
I'm not sure why you're running out of memory. [:(] I did notice that your logs have a lot (10,000 lines?!) of Temporary File logs that mine don't:
[quote]
2014-07-16 11:39:28.3801 7 Info TemporaryFileSearchResultReader Creating temporary file for search hits at 'C:\Users\AWALT\AppData\Local\Temp\tmp791.tmp'.
2014-07-16 11:39:28.3811 7 Info TemporaryFileSearchResultReader Wrote 1 hits from 1 results (0.00 MB) in 00:00:00.0001462.I don't know what's causing that and it could be related. Maybe try clearing out C:\Users\AWALT\AppData\Local\Temp\ and re-running the Guide?
0 -
Maybe try clearing out C:\Users\AWALT\AppData\Local\Temp\ and re-running the Guide?
I keep that cleaned out, I did delete everything (4 files stayed in there because they were open), ran it again - crashed within about 3 minutes.
0 -
Oops here are the logs in case they show something else:
0 -
What is the conclusion on this - is it to be filed as a bug, is there additional troubleshooting needed, etc.? Thanks!
0 -
Someone at Logos ought to be able to answer this or narrow it down. My guess is it is one of: a) a corrupt resource; b) a corrupt DB; c) a bug in the indexing/tagging; or d) you have many more resources than either Dylan or I (~10k) tested with. I don't know how to narrow this down.
I do think it odd that it seems to have created around 5300 temp files on your system whereas it only created about 180 on mine. (I also think it extremely odd that it's creating so many small temp files at all. Seems inefficient, but that's just backseat speculation.)
0 -
Don: I suggest you call tech support and have them connect to your computer remotely (if they are willing to look at a beta).
It would help Logos as much as it helps you.
0 -
It seems like a bug, but we'll have difficulty solving it unless we can get a consistent repro.
I ran a "Gen-Rev" Passage Guide (Sermons only) against all resources available for Logos. My system logged the creation of hundreds of temp files (like Don's), but didn't even come close to running out of memory. (Maximum usage was about 600MB.) So I'm still not sure what is causing this.
0 -
Maybe I'm stating the obvious, but the quickest way is for tech support to get on Don's machine. It could be something idiosyncratic about the HDD/SSD and the driver, or a wider issue.
And wondering ALOUD if beta versions have debug builds as well as hashes to ensure program integrity and easier troubleshooting.
0 -
the quickest way is for tech support to get on Don's machine
We don't offer phone support for beta releases; if Don calls in, they'll very likely refer him to the forums.
0 -
Yes, I figured that might be the case.
But isn't Logos the least bit curious? It would help Logos as much as it helps Don. [:)]
0 -
Don, is this your only Logos install? Do you have another desktop or laptop with Logos you can test this on? I don't expect it would crash but it would eliminate any setting or user data interaction (which I wouldn't expect to exist); the fault could more likely be localized to that one particular install.
0 -
could it be possible that we are encountering a memory fault at an address that is rarely used?
Windows 8 (and 7 if I remember correctly) has a memory test tool.
Additionally one could run prime95 just as a sanity check that its Logos and not an ailing piece of hardware.L2 lvl4 (...) WORDsearch, all the way through L10,
0 -
I ran this test on my other laptop, and it ran fine. So I thought I wonder if the index is corrupted. So I started a Rebuild Index. It only ran for about 3 minutes and then it ended. I have attached the index log (there was no crash or anything), you can see it says the index ended prematurely:
2014-07-17 19:09:26.3241 13 Info BibleIndex (0ms) Attempting to replace index 'C:\Users\AWALT\AppData\Local\Verbum\Data\ds5emrgk.0lc\BibleIndex/index' with new index 'C:\Users\AWALT\AppData\Local\Verbum\Data\ds5emrgk.0lc\BibleIndex/index-build'.
2014-07-17 19:09:26.3511 13 Info BibleIndex Library indexing canceled, failed, or ran out of storage space; deleting temporary files.Does this make any sense?
I have restarted and the Rebuild index has restarted. We will see how far it gets.
0 -
Congratulations, you have been "entrusted with a mystery". [:)]
0 -
Well I finished the complete reindex and ran the test again, it crashes in not even a minute. No way memory is used up that quickly (and it has never even been close when I have watched Perf Mon in the past).
ANy idea what to try, it seems like something is corrupted - a catalog to delete etc.?
0 -
Sorry to sound like a broken record. Best thing now is for tech support to consider the wider interests, and get on your machine to track down this SHOWSTOPPER bug.
0 -
Tried deleting the catalog.db and journal, same thing.
0 -
If Logos does not want to look into this case more closely, Don maybe you should just get out of the beta channel for now.
0 -
I have now tried on two other machines, one the Gen-Rev worked, the other it crashed. So it's not just unique to one computer.
Of the two of three that crashed, they were older installs that have been through lots of upgrades. The one that did not crash is newer. So my next attempt if to take one of the laptops that crashed, and I am reinstalling Verbum and will then see if it works. If so, this will be the second time (first was a year or two ago as I recall) that something gets so corrupted you just have to reinstall everything. Stay tuned.
0 -
Sorry you had to do a re-install. If it works it seems like you narrowed it down to a resource problem, having already rebuilt the indices. My guess is the code is encountering something unexpected in a version of a resource or the index created from a resource that's causing it to eat resources (maybe infinite recursion/loop?). "Update Resources" may fix the other crashing system. If it does, would love to see the logs from the update. Just another WAG.
0
