Sigh... third crash today.
Doing general work, had just run a Basic query on whole library, went directly to open a resource — boom.
Logos log and Apple Crash report attached.
4478.20121124-02Logging.zip
1050.Logos_2012-11-24-171331_Patricks-iMac.crash.zip
According to your logs it is a TargetInvocationException. The problem appears to be something unique to Mac (at least I have not experienced it, nor can I reproduce it).
This user also had this crash, though he seems to have been doing something different http://community.logos.com/forums/t/60618.aspx
The best advice I could give would be to sell your Mac equipment and buy Windows machines [;)]
Just kidding about that part, but I think Logos is going to have to address this one unless there Mac users who have figured something else out.
Appears Logos 5.0a was launched after the crash, which overwrote contextual crash information in Logos.log file.
LogosCrash.txt has a stacktrace crash at 17:13:26, but Logos.log starts at 17:13:39 and looks OK.
Personally first time have seen asychronization error with "unable to open the database file". Previously have seen similar error message with "too many open files"
If (when) crash repeats, please compress Logging folder before launching Logos 5 for OS X application.
Keep Smiling [:)]
Appears Logos 5.0a was launched after the crash, which overwrote contextual crash information in Logos.log file. LogosCrash.txt has a stacktrace crash at 17:13:26, but Logos.log starts at 17:13:39 and looks OK.
I will keep that in mind, I have seen Logos.log files with multiple crash info in them, the latest being the same as what is reported in the LogosCrash.txt file. But obviously to be safe I will zip files before restarting Logos.
Anyway... I hope all these crashes are being reviewed by Logos devel. team and that there will be a fix soon. I hope there is not a major problem with the new Mono version, is it version 3.x in Logos 5 isn't it, which is quite new only having been released on October 2012.
