"Logos Bible Software 4 quit unexpectedly"

Page 1 of 1 (2 items)
This post has 1 Reply | 1 Follower

Posts 524
Stuart Robertson | Forum Activity | Posted: Tue, Dec 6 2011 2:17 PM | Locked

I think I've now achieved a new record for Logos' continual crashing. Not sure what's changed or why Logos has a newfound passion for crashing, but this is getting annoying. And, yes, I know I'm using a beta. For good reason - I'm hoping that the bugs that plague me (did I mention 15 seconds to apply highlighting, etc etc etc) can be fixed and I can use Logos without it getting in the way. Yes, I know betas can be unstable. But compared to the bugs and irritations in the "stable" version there's not much choice here.

Logs are attached (assuming logging is enabled - I seem to recall somewhere that recent betas have disabled logging). Anyway, these log files were created by Logos Log Scribe.0027.LogosLogs Stuart Robertson 20111206-093700.gz

Running on 17" Macbook Pro (late 2010 model), 8GB RAM, OS X 10.7.2, Logos 4 latest beta (beta 8)

Posts 15805
Forum MVP
Keep Smiling 4 Jesus :) | Forum Activity | Replied: Tue, Dec 6 2011 6:37 PM | Locked

Stuart Robertson:
Logs are attached (assuming logging is enabled - I seem to recall somewhere that recent betas have disabled logging).

Logos4.log file includes message about Indexer logging disabled.  Logos4.log file is dated from 2 Dec 2011 that shows Mac has not been restarted for some time since Logos 4 Mac process number was 96,989 (after restart, processes start numbering at 1).  Unfortunately, Logos 4 Mac has some memory leakage that needs a restart of OS X to clear.  Also noted some strange console error messages inside Logos4.log file: "Unsupported window created of class: FindBarWindow" , "Unsupported window created of class: FindBarWindow" and "Unsupported window created of class: PopupWindow"

Likewise noticed font scaling being used; Logos 4.5 Beta includes many more Font Sliders.

Wiki Mac Troubleshooting  => How to Report Bugs in Logos 4 Mac  includes link to 5504.Logos4MacLogging.app.zip (display logging setting, then optionally change).  Please enable logging, then use Logos Log Scribe after a crash happens (before opening Logos 4 Mac again).  Posted Logos4.log file did not have crash information (had normal exit).

Stuart Robertson:
Running on 17" Macbook Pro (late 2010 model), 8GB RAM, OS X 10.7.2, Logos 4 latest beta (beta 8)

Apologies: looking at Apple's support site, could find Mid 2010 and Early 2011 MacBook Pro 17" models, but not late 2010.  Wondering if Mid 2010 specifications match your computer => http://support.apple.com/kb/SP581 ?

If so, wonder about trying both graphics processors with Logos 4 Mac.  The Intel HD graphics shares main memory while the GeForce 330 GT has dedicated graphics memory.  Apologies: not know about Logos 4 Mac stability when sharing main memory for graphics in OS X Lion (wondering about potential for memory collisions and leaks that feed frustration factor).

Apple's System Preferences has graphics setting in Energy Saver => http://www.lancelhoff.com/switching-video-cards-macbook-pro/

CNET review => http://reviews.cnet.com/8301-13727_7-20004619-263.html includes link to => http://codykrieger.com/gfxCardStatus/

A month after OS X Lion release, one article describes graphic driver issues => http://reviews.cnet.com/8301-13727_7-20091204-263/graphics-issues-plaguing-os-x-10.7-lion-upgrades/  with follow-up article last month => http://reviews.cnet.com/8301-13727_7-57332340-263/macbook-pro-systems-freezing-despite-video-update/

Caveat: using more powerful graphics also generates more heat along with draining batteries faster.  If MacBook Pro feels hot to touch, may want to use a laptop cooler.

Keep Smiling Smile

Page 1 of 1 (2 items) | RSS