B6 Beach Ball of Death

After updating to B6, when I open L4 the program gives me the music and then the beach ball comes and a minute later the program crashes.

Also, I tried hard to follow the instructions for making a post. But I am not sure about a logging folder or the other .log files.

Thanks,

2350.Console Messages.log.zip

Find more posts tagged with

Comments

Stephen Owens

My problem with reporting correctly is that the file that the video and instructions requires is said to no longer be needed. So, I guess I only need to give the console log file. Otherwise, I would need instructions on how to obtain the other .log files.

Thanks,

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/161154#Comment_161154

My problem with reporting correctly is that the file that the video and instructions requires is said to no longer be needed. So, I guess I only need to give the console log file. Otherwise, I would need instructions on how to obtain the other .log files.

No longer need to download and copy nlog.config file to logging folder to enable logging. Also video does not mention SyncClientErrors.log file (created if sync errors happen). Log file set for posting is: console messages, Logos4.log, & Indexer.log - if SyncClientErrors.log file exists, please include with other logs.

Posted console messages has a memory allocation (malloc) error. In forum http://community.logos.com/forums/p/21204/159177.aspx, a Logos developer extraordinaire asked:

Looks like the app ran out of memory trying to malloc. Since we're 32-bits, this happens at around 2.37 GB of Active Memory used. Any idea how you got the app into that scenario?

Likewise wonder about steps causing Logos 4 to run out of memory to allocate ?

Personally learned to monitor Active Memory usage. Already configured Activity Monitor to show memory usage on dock - now pay attention to green and yellow sizes - if Green too small, spinning beach balls happen. If Yellow too large (many open programs), can easily crash Logos 4 Mac.

Keep Smiling [:)]

Stephen Owens

https://community.logos.com/discussion/comment/161205#Comment_161205

It runs out of memory with it being the only app open. I have an I7 macbook pro with 4gb mem. Also, the home page on logos just has the gear spinning.

Stephen Owens

https://community.logos.com/discussion/comment/161205#Comment_161205

"Log file set for posting is: console messages, Logos4.log, & Indexer.log - if SyncClientErrors.log file exists, please include with other logs."

How do I create such logs... I have wanted to report crashes before but the video DOES NOT instruct how to obtain these logs. The only log it shows is through the console. Of course, I may be missing something but I have watched the video five times. Please, help with this it is frustrating.

BTW -- I am having the same problem as the user who has crash on start up. The program opens and uses up all the memory and then crashes.

Thanks,

Cameron Watters (Faithlife)

https://community.logos.com/discussion/comment/161250#Comment_161250

How do I create such logs... I have wanted to report crashes before but the video DOES NOT instruct how to obtain these logs. The only log it shows is through the console. Of course, I may be missing something but I have watched the video five times. Please, help with this it is frustrating.

Starting at 0:43, Joe begins explaining that you need to grab all the logs out of your Logging directory. He even recommends that you pin it to your dock. What isn't explicit in the video is the location of that logging directory:

/Users/<yourusername>/Library/Application Support/Logos4/Logging

We need all of the logs from that directory. You don't need to do anything to create them, we do that for you. The Console Messages.log is actually a system-wide log that catches errors that cannot be caught in application-specific logging. Grabbing it is more involved, so it gets a lot more time in the video.

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/161250#Comment_161250

BTW -- I am having the same problem as the user who has crash on start up. The program opens and uses up all the memory and then crashes.

Concur crashes happening - however, different symptoms (error messages) appear in Console Messages => different problems.

Keep Smiling [:)]

Stephen Owens

https://community.logos.com/discussion/comment/161261#Comment_161261

Ahhh... that's what I needed. Will post directly.

Thanks,

Stephen Owens

https://community.logos.com/discussion/comment/161266#Comment_161266

Here it is...52332.Archive.zip