I've had random crashes over the last few days. Logs attached.
1882.LogosLogs.lankox.20150808-100204.zip
Did these logs come AFTER a crash but BEFORE you restarted? Just curious since I don't see a crash log. There is, however, a logos.log file from last night. I do see the following in your logos.log file: "Got a SIGSEGV while executing native code" which relates to mono somehow.
Does it crash immediately upon startup? Have you tried using a different layout (perhaps you have a corrupted layout which needs to be rebuilt)?
I don't remember if I created the log file before or after restarting Logos. What is the correct procedure? When Logos crashes, most of the time I'm not using the program but it is running in the background. I can always get Logos to crash by opening up atlas then hitting "Open in Google Maps".
I don't remember if I created the log file before or after restarting Logos. What is the correct procedure?
When you start Logos, it wipes previous logs and creates new ones. So you need to archive logs after a crash but prior to restarting Logos.
Logos just crashed again while I was perusing the Mac Console application. Here are the attached logs before restarting Logos but I still don't see a crash log. Console reports this.
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGABRT)Exception Codes: EXC_I386_GPFLT
Application Specific Information:abort() called
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread0 libsystem_kernel.dylib 0x00007fff86968286 __pthread_kill + 101 libsystem_c.dylib 0x00007fff90fecb53 abort + 1292 libmonosgen-2.0.1.dylib 0x00000001110bd721 mono_handle_native_sigsegv + 8493 libmonosgen-2.0.1.dylib 0x0000000110fbe01e mono_sigsegv_signal_handler + 3664 libsystem_platform.dylib 0x00007fff84474f1a _sigtramp + 265 ??? 0xb785191b1c8d90ea 0 + 132240034850771806506 com.apple.CoreFoundation 0x00007fff8ef4d3f9 __CFRUNLOOP_IS_SERVICING_THE_MAIN_DISPATCH_QUEUE__ + 97 com.apple.CoreFoundation 0x00007fff8ef0868f __CFRunLoopRun + 21598 com.apple.CoreFoundation 0x00007fff8ef07bd8 CFRunLoopRunSpecific + 2969 com.apple.HIToolbox 0x00007fff8d07f56f RunCurrentEventLoopInMode + 23510 com.apple.HIToolbox 0x00007fff8d07f1ee ReceiveNextEventCommon + 17911 com.apple.HIToolbox 0x00007fff8d07f12b _BlockUntilNextEventMatchingListInModeWithFilter + 7112 com.apple.AppKit 0x00007fff8e3978ab _DPSNextEvent + 97813 com.apple.AppKit 0x00007fff8e396e58 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 34614 com.apple.AppKit 0x00007fff8e38caf3 -[NSApplication run] + 59415 com.logos.Logos 0x000000010dd82c42 DesktopApplicationMain + 51816 com.logos.Logos 0x000000010dd82cb2 main + 917 libdyld.dylib 0x00007fff880015c9 start + 1
6685.LogosLogs.lankox.20150808-162935.zip
When Logos crashes, most of the time I'm not using the program but it is running in the background. I can always get Logos to crash by opening up atlas then hitting "Open in Google Maps".
With this latest crash, was it the former or the later?
When Logos crashes, most of the time I'm not using the program but it is running in the background. I can always get Logos to crash by opening up atlas then hitting "Open in Google Maps". With this latest crash, was it the former or the later?
The former. I was looking at the Logos log in the Mac console application when Logos quit.
I can also make 6.4 on Mac crash with the same process: i'll open a case for this.
We are no longer able to reproduce this. Is the software still crashing when you Open in Google Maps?
Seems to be fixed on the latest release. Thanks!
