A 18--Activity busy, then crashed

1. I opened L4 and did a search for a passage. It all seemed to work fine.

2. I looked for another Bible (NLT), which seemed to take some time--about a minute to get through my library

3. Then I left it open to do some work on email. I noticed my fan running at high speed, so checked my "Activity Monitor" and saw the following": 2872 Logos Bible Software 4 Dave 186.4 29 465.71 MB Intel 1.58 GB. The "CPU" for L4 was running at 186.4. There was no search going on, nor did I see the indexing icon working. So I'm not sure what was going on.

4. Then as I was preparing this report, L4 just crashed.

3324.Archive.zip

Thanks!

Find more posts tagged with

Comments

David Whitaker

Here's a screen shot of my activity monitor--if that will help:

Thomas Ball

https://community.logos.com/discussion/comment/120991#Comment_120991

David:

Could you be a bit more explicit with your steps? For instance for step one, did you do a search for the passage (which passage) from the HomePage? And in step two, what do you mean you looked for another bible? Did you use the command bar? The Library window? Finally, is this reproducible? Thank you for the logs by the way.

David Whitaker

https://community.logos.com/discussion/comment/121001#Comment_121001

Yes, it is repeatable:

1. I opened up L4 and typed in "Isa 29" and hit the "go" button

2. Within a few seconds, I could start to here the fan starting to run faster

Here's the screen shot of L4, followed by the screen shot of my Activity Monitor and current log

5417.Archive.zip

David Whitaker

https://community.logos.com/discussion/comment/121013#Comment_121013

I forgot to mention that I have to "force quit" to close L4

Thanks for your quick response!

Thomas Ball

https://community.logos.com/discussion/comment/121014#Comment_121014

David:

Looking at the screenshot it seems you are doing a guide for the entire chapter. Could you tone down the range a bit and see if you have similar results?

David Whitaker

https://community.logos.com/discussion/comment/121019#Comment_121019

That made a difference:

Thomas Ball

https://community.logos.com/discussion/comment/121021#Comment_121021

David:

I thought this might be the case. When I tried it on the Mac mini I have here at work it crashed trying to do that search (unsurprisingly). It even took a very long time on the imac with double the RAM and 3x the CPU.

J.R. Miller

https://community.logos.com/discussion/comment/121024#Comment_121024

Tommy, just to clarify and maybe alleviate any concerns from those reading along. The crash is due to memory leaks of some kind, but once these get optimized in the Beta cycle, these larger searches should not be a problem. Correct?

David Mitchell

https://community.logos.com/discussion/comment/121107#Comment_121107

Tommy, just to clarify and maybe alleviate any concerns from those reading along. The crash is due to memory leaks of some kind, but once these get optimized in the Beta cycle, these larger searches should not be a problem. Correct?

Correct. In fact, I'm working on some of those optimizations right now (well, right now, I'm writing a forum post, but you get the idea...). No promises when it will get in, but some of this stuff should speed up before beta.