BUG: CRASH in 5.2b beta 3
I had a standard Passage Guide up, but all the sections were closed except for the Sermons section was added. I was looking at John. Then seeing the thread about new Sermons, I typed in Gen-Rev to get all of the Bible up, as someone suggested. It generated quickly as all the sections came up closed. I added the Sermons section again, and it crashed. This is Verbum, beta.
Note, I brought Verbum back up, and first thing, from the Home Page typed Gen-Rev, and the Passage Guide/Exegetical Guide came up but it was gray and the Sermons section was just "thinking", and then it eventually crashed. That's the second Log File zip here:
Comments
-
I wasn't able to reproduce the OutOfMemoryException when running the Sermons section on Gen-Rev; memory usage didn't increase significantly in my testing.
Your logs show a huge amount of background activity going on, though; the logging's not precise enough to identify what it is, but I suspect Visual Filters. (I'll make a note that additional logging is necessary here.) Besides possibly consuming application memory, these VFs are possibly slowing down your system. If there are old ones you don't need any more, you could consider deleting them, or right-clicking and choosing "Do not show in any resources".
0 -
Thanks Bradley for your investigation! I have 41 Visual Filters, is that considered a lot? Anyway, I turned them all off (Do not show in any resource), I restarted Verbum ran "Gen-Rev" from the Home page, and the system crashed again Here are the logs in case they show something new (PS, this is on a different computer, as I am not home now, but same thing happens eliminating a corrupt install or something I assume):
0 -
Bradley, since I have documents.logos.com to undelete deleted documents, I went ahead and deleted every one of my visual filters, sync'd, closed and restarted Verbum. Did the same PG, and it still crashed, so I don't think it's Visual Filter related. Here are the logs from that exercise:
0 -
Good thinking!
In this log, it looks like you ran a regular PG and EG on Gen-Rev. Are any sections open other than Sermons? (While Sermons shouldn't use much memory to run on the whole Bible, other sections may.)
It would be useful to know if Sermons itself causes the problem, or some other section. You could test this by creating a custom Guide Template that only contains Sermons, close all panels, then open that custom Guide. What's the memory usage of Logos before opening that Guide? Does it just keep increasing until Logos crashes when you run Sermons on Gen-Rev?
0 -
OK I created a custom guide, just Sermons. I closed and reopened Verbum, and let it sit a minute - it was at about 260MB of memory. I ran the Gen-Rev, took about a minute or so, and the results returned - it got to 460MB. This laptop has 32GB so it as only using 28% of total memory or so according to the status line of the Performance Monitor. It eventually gave more memory back and got back to 263MB.
I exited and restarted Verbum, ran the Gen-Rev from Home Page again, it crashes, but memory is only 478MB. All the sections are closed, so I don't think it is another section there. Exegetical Guide has all sections closed too. But - I have noticed that Text Comparison comes up, and it's little wheel is spinning while the PG is working. Maybe it's Text Comparison? Mine has 5 Bibles - NAB, RSV2CE, ESV, NASB95, NIV.
I restarted, and brought up just Text Comparison, and did Gen-Rev. I noticed after the fact it had a different set of Bibles - sblgnt, logos wh, na28, byz. Memory got close to 1GB and Verbum was frozen, so I killed the process. I restarted doing Gen-Rev with NAB, RSV2CE, ESV, NASB95, NIV in a TC. THAT crashed it! Memory only got to about 800MB. The wheel froze for about 10 seconds, then Verbum crashed. Logs attached.
0 -
Don Awalt said:
ran the Gen-Rev from Home Page again, it crashes
This opens a lot of guides and tools, and it's likely that one of them is using too much memory and crashing. Your research seems to indicate that (at least) Text Comparison is to blame; there may be others.
Unfortunately, while Logos is a 32-bit app, it can't access more than about 1GB of memory, so asking it to crunch a lot of data is likely to fail.
If we restrict this to try to prevent crashes (e.g., the 15-verse limit in EG), we get complaints about the restriction. If we don't restrict it, we get OutOfMemoryException crash reports. And the middle ground: detecting the out-of-memory condition and responding appropriately is actually extremely difficult; it would be far better for us to spend that time porting Logos to 64-bit which would avoid the problem.
0 -
For now, running TC on Gen-Rev kind of falls in the "Doctor, it hurts when I do this..." category. [:)]
0 -
Yeah but it took some work to figure out that was where the pain was coming from when it's one of quite a few panels up [:)]
0 -
Bradley Grainger (Logos) said:
... it would be far better for us to spend that time porting Logos to 64-bit which would avoid the problem.
Is that an "insider's leak"? I'm really looking forward to Logos filling up my RAM if that means speed ...
0 -
Lee said:Bradley Grainger (Logos) said:
... it would be far better for us to spend that time porting Logos to 64-bit which would avoid the problem.
Is that an "insider's leak"? I'm really looking forward to Logos filling up my RAM if that means speed ...
More than a leak as it has been mentioned a number of times although I expect it won't show until L6, next year+.
0
