Logos 4 crashes on startup in Mountain Lion
when starting up, logos just crashes with a kernel exception. 353267.Archive.zip
Comments
-
Vickie, all I see in your log is the stacktrace. Do you have diagnostic logging enabled? http://wiki.logos.com/Diagnostic_logging
0 -
Yes, Logging is enabled. It crashes immediately upon the icon bouncing in the tray, so I don't think it's even getting to a place where it would normally log something useful. the sequence is click the icon, watch it bounce once and poof the crash screen.
in the stack trace it appears there is a kernel exception seemingly thrown by mono when it tries to load a module of some kind. i did a fresh download from the web site and told it to replace the app in the Applications folder, which usually replaces the whole package with downloaded files, but it still has the problem.
so, in my mind it seems one of the companion libraries is damaged, but i can't find which one it is and don't know how to get a fresh replacement even still. it could also be some sort of damaged configuration of logos on my mac but again, not sure how to tell if the configuration is damaged.
thanks
0 -
Here's the information from the popup (or the first half. the second half looks like checksums of binary images...
Process: Logos Bible Software 4 [17903]
Path: /Applications/Logos Bible Software 4.app/Contents/MacOS/Logos Bible Software 4
Identifier: com.logos.Logos_Bible_Software_4
Version: 4.60.2972 (61460.11.156)
Code Type: X86 (Native)
Parent Process: launchd [144]
User ID: 501
Date/Time: 2012-09-05 21:16:10.499 -0600
OS Version: Mac OS X 10.8.1 (12B19)
Report Version: 10
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00000000ac801000
VM Regions Near 0xac801000:
__OBJC 00000000ac800000-00000000ac801000 [ 4K] rw-/rwx SM=COW /usr/lib/libobjc.A.dylib
--> Submap 00000000ac801000-00000000ac802000 r-x/rwx process-only submap
__IMPORT 00000000ac801000-00000000ac802000 [ 4K] rw-/rw- SM=COW /usr/lib/libobjc.A.dylib
Application Specific Information:
abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x98fd8a6a __pthread_kill + 10
1 libsystem_c.dylib 0x9052bacf pthread_kill + 101
2 libsystem_c.dylib 0x90562508 abort + 168
3 libmono-2.0.1.dylib 0x00bde0cc mono_handle_native_sigsegv + 908
4 libmono-2.0.1.dylib 0x00b0ea5f mono_sigsegv_signal_handler + 351
5 libsystem_c.dylib 0x9051686b _sigtramp + 43
6 ??? 0xffffffff 0 + 4294967295
7 libmono-2.0.1.dylib 0x00b0e900 mono_sigill_signal_handler + 96
8 libobjc.A.dylib 0x952e0bda object_setInstanceVariable + 80
9 com.apple.AppKit 0x9681d461 -[NSNibOutletConnector establishConnection] + 486
10 com.apple.AppKit 0x967ef15f -[NSIBObjectData nibInstantiateWithOwner:topLevelObjects:] + 1002
11 com.apple.AppKit 0x967cd762 loadNib + 373
12 com.apple.AppKit 0x967ccb3a +[NSBundle(NSNibLoading) _loadNibFile:nameTable:withZone:ownerBundle:] + 233
13 com.apple.AppKit 0x9691d774 +[NSBundle(NSNibLoading) loadNibFile:externalNameTable:withZone:] + 154
14 com.apple.AppKit 0x967cc80f +[NSBundle(NSNibLoading) loadNibNamed:owner:] + 709
15 com.apple.AppKit 0x967c8688 NSApplicationMain + 447
16 com.logos.Logos_Bible_Software_4 0x0000d40a start + 54
Thread 1:
0 libsystem_kernel.dylib 0x98fd90ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9052d04c _pthread_workq_return + 45
2 libsystem_c.dylib 0x9052ce19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x90514cca start_wqthread + 30
Thread 2:: Dispatch queue: com.apple.libdispatch-manager
0 libsystem_kernel.dylib 0x98fd99ae kevent + 10
1 libdispatch.dylib 0x97ff5cc5 _dispatch_mgr_invoke + 993
2 libdispatch.dylib 0x97ff57fd _dispatch_mgr_thread + 53
Thread 3:
0 libsystem_kernel.dylib 0x98fd90ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9052d04c _pthread_workq_return + 45
2 libsystem_c.dylib 0x9052ce19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x90514cca start_wqthread + 30
Thread 4:
0 libsystem_kernel.dylib 0x98fd90ee __workq_kernreturn + 10
1 libsystem_c.dylib 0x9052d04c _pthread_workq_return + 45
2 libsystem_c.dylib 0x9052ce19 _pthread_wqthread + 448
3 libsystem_c.dylib 0x90514cca start_wqthread + 30
Thread 5:
0 libsystem_kernel.dylib 0x98fd67d2 mach_msg_trap + 10
1 libsystem_kernel.dylib 0x98fd5cb0 mach_msg + 68
2 libmono-2.0.1.dylib 0x00c4f471 mach_exception_thread + 97
3 libmono-2.0.1.dylib 0x00de8808 GC_start_routine + 120
4 libsystem_c.dylib 0x9052a557 _pthread_start + 344
5 libsystem_c.dylib 0x90514cee thread_start + 34
Thread 6:
0 libsystem_kernel.dylib 0x98fd8c72 __semwait_signal + 10
1 libsystem_c.dylib 0x905b4a6d nanosleep$UNIX2003 + 189
2 libmono-2.0.1.dylib 0x00d897c8 collection_thread + 56
3 libsystem_c.dylib 0x9052a557 _pthread_start + 344
4 libsystem_c.dylib 0x90514cee thread_start + 34
Thread 7:
0 libsystem_kernel.dylib 0x98fd680e semaphore_wait_trap + 10
1 libmono-2.0.1.dylib 0x00dbc1d2 mono_sem_wait + 50
2 libmono-2.0.1.dylib 0x00c9a5a2 finalizer_thread + 114
3 libmono-2.0.1.dylib 0x00d64291 start_wrapper_internal + 641
4 libmono-2.0.1.dylib 0x00d64387 start_wrapper + 23
5 libmono-2.0.1.dylib 0x00dab05e thread_start_routine + 206
6 libmono-2.0.1.dylib 0x00de8808 GC_start_routine + 120
7 libsystem_c.dylib 0x9052a557 _pthread_start + 344
8 libsystem_c.dylib 0x90514cee thread_start + 34
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x9051684e ecx: 0xbffff08c edx: 0x98fd8a6a
edi: 0xac09ba28 esi: 0x00000006 ebp: 0xbffff0a8 esp: 0xbffff08c
ss: 0x00000023 efl: 0x00000206 eip: 0x98fd8a6a cs: 0x0000000b
ds: 0x00000023 es: 0x00000023 fs: 0x00000000 gs: 0x0000000f
cr2: 0xac096144
Logical CPU: 0
0 -
Vickie Weers said:
Yes, Logging is enabled. It crashes immediately upon the icon bouncing in the tray, so I don't think it's even getting to a place where it would normally log something useful.
Vickie - Have you updated to 10.8.1? Also, have you tried to download the mac engine and reinstall a new copy over Logos (not an uninstall!)? You can download the engine here: Logos 4 Mac Installer
0 -
My previous reply before the error message, I had said that I had the most recent update to Mountain Iion and had tried a fresh reinstall on my Logos.
0 -
Vickie, I showed your logs to a Dev and the problem isn't super obvious based on your logs. I've asked Tech to have someone contact you to investigate the issue further.
0 -
Okay, by phone or email?
0 -
Hi, I am having this same problem too. I already tried installing over the app, and tried uninstall and install next too. Still having those crashes.
I am leaving here my logging folder with the files, if you would be so kind to help.
Thank you.5582.Logging (Logos).zip0 -
Hello Tiago,
I will contact you offline about this.
0 -
Not sure if this is the same problem but I can't open Logos either. im on 10.8.1. it was working fine then I did a shut down by holding down the power button. after restart I can't get it to do anything. just get a message that it shut down improperly last time.
0 -
what exactly does the reinstall do?
0 -
Sam Pedigo said:
Not sure if this is the same problem but I can't open Logos either. im on 10.8.1.
You need to post logs to find out. [;)]
0 -
-
I went ahead and called in. somehow my data got corrupted by shutting down while it was updating. Anyway, he worked on it for a bit now am waiting for fresh download and indexing to finish. I guess God wants me to watch LOST today and not work on sermon. sweet.
0 -
This appears to be a problem with 10.8.1; there are reports of Apple's own applications failing to launch in the same manner after installing 10.8.1. People have found success in getting their application to launch again by:
- Open Terminal
- Type sudo update_dyld_shared_cache -force
- Enter your password
- Reboot your machine
Mac Developer
Faithlife0 -
I'm having the same problem here it looks like. I upgraded to Mountain lion and now Logos 4 doesn't work. I tried downloading the engine mentioned earlier in this feed but I still can't get logos 4 to open. It crashes every time.
0 -
-
-
-
-
I entered in terminal defaults write com.logos.Logos_Bible_Software_4 LoggingEnabled -bool YES but I don't see the logs anywhere at least not where they were before
0 -
I enabled logging but I can't find anything called logos.log
0 -
-
Yes, I started up Logos 4 and it crashed showing the Mac logs on the screen but when I went to look for the logos log you mentioned I can't find it.
0 -
I just ran it again and here is a sample of what comes up on the screen.
0 -
Robert Davis said:
I went to look for the logos log you mentioned I can't find it.
From the wiki:
Crash and Log files are written to ~/Library/Application Support/Logos4/Logging folder (~ is your personal home directory). By default, OS X Lion hides ~/Library folder, with many ways to see contents => http://www.macworld.com/article/161156/2011/07/view_library_folder_in_lion.html and can assign keyboard shortcut =>http://mac.finerthingsin.com/post/7849528212/lion-library-folder-visible
http://wiki.logos.com/Diagnostic_Logging#Mac
If you are still able to edit your last post, please delete the apple log… it isn't needed. In the future, please only attach logs via the paperclip icon. Reading logs in the forums is near impossible, and it makes reading the thread more difficult.
0 -
ok I am able to find this folder Library/Application Support/Logos4/Logging but there are only 2 files in there... .DS_store and indexer.log
0 -
-
