BUG: Crash on Bible Search

My beta installation of 4.5b b6 is crashing whenever I do a bible search. It is consistently repeatable, and does not matter what I search for. I have a crash txt & an error log.

8080.Logos4Error.log

6378.Logos4Crash.txt

(By the way, what is an awesomium log?)

((Nevermind... http://awesomium.com/ ))

Find more posts tagged with

Comments

Keep Smiling 4 Jesus :)

Curious about Bible search ? word(s), passage, resource(s) ?

Also wonder if crash repeats when diagnostic logging is enabled ? If so, would like to look at Logos4.log file.

Keep Smiling [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/358717#Comment_358717

Also wonder if crash repeats when diagnostic logging is enabled ? If so, would like to look at Logos4.log file.

Yes… but it did not create a new Logos4.log file.

Curious about Bible search ? word(s), passage, resource(s) ?

Anything & everything. (No I did not search for "God" or "the" [:)]) One of my searches was for "hovered."

I need to take my son out to play. [:)] I will try to get another Logos4.log file (although two attempts didn't work).

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/358736#Comment_358736

Curious about Bible search ? word(s), passage, resource(s) ?

Anything & everything. (No I did not search for "God" or "the" ) One of my searches was for "hovered."

Apologies: unable to replicate crash using Logos 4.5b Beta 6 on Mac OS X 10.6.8

After Bible search for "hovered" completed quickly, did a search for God that took longer (about a minute on a 27" iMac):

I need to take my son out to play. I will try to get another Logos4.log file (although two attempts didn't work).

Option: could download and use 5504.Logos4MacLogging.app.zip to display your logging setting, then change to enable logging.

the applescript application uses the terminal commands in wiki => http://wiki.logos.com/Diagnostic_Logging#Mac

Keep Smiling [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/358755#Comment_358755

KS4J -

I was able to get a log via the script you wrote. Question: To enable logging for one session, you are supposed to just hold down the command key just after starting, right? (This also brings up the open to blank layout screen). Right? If so, there may be ANOTHER bug. [:)]

0564.Logos4.log

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/358816#Comment_358816

To enable logging for one session, you are supposed to just hold down the command key just after starting, right? (This also brings up the open to blank layout screen). Right? If so, there may be ANOTHER bug.

+1 confirmation for command key bug since Logos4.log file is not created when command key is used and logging is disabled.

Keep Smiling [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/358836#Comment_358836

+1 confirmation for command key bug

I created a new thread for this issue HERE. [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/358839#Comment_358839

KS4J - I forgot to ask... Did my log show anything useful?

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/358859#Comment_358859

KS4J - I forgot to ask... Did my log show anything useful?

Yes, the Logos4.log file has an error message:

Logos Bible Software 4[6292:3a03] Could not find image named 'GoldStar'.

that was a bit puzzling plus showed process number is 6,292 so know has been awhile since Mac OS X rebooted, which resets process number to 1.

Also, Logos4.log file ends with a crash and error message: "Too many open files"

Keep Smiling [:)]

JT (alabama24)

https://community.logos.com/discussion/comment/358871#Comment_358871

showed process number is 6,292 so know has been awhile since Mac OS X rebooted

I leave my computer on most of the time... BUT... I restarted it a couple of times last night! Does the process number sound weird to you with that info?

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/358873#Comment_358873

showed process number is 6,292 so know has been awhile since Mac OS X rebooted

I leave my computer on most of the time... BUT... I restarted it a couple of times last night! Does the process number sound weird to you with that info?

With an Apple Java update today, also restarting my iMac (was up to process number 16,328 for Logos 4 so know process number can go higher).

Keep Smiling [:)]

Keep Smiling 4 Jesus :)

https://community.logos.com/discussion/comment/358839#Comment_358839

+1 confirmation for command key bug

I created a new thread for this issue HERE.

Using Logos 4.5b (4.52.0.2176) can replicate command key not enabling diagnostic logging for a session.

Updated Feature Parity list with reference to thread => BUG: Command Key Logging

PC Launch has option to enable diagnostic logging while command key does not enable logging on Mac – Logos 4.5b regression

Keep Smiling [:)]