I can only think that I have been tagging for a few hours and forgot to re-start L5 and crashed into the usual 'memory leak'.
Logs attached in case I am wrong (not an unusual event.)
3365.LogosLogs Martin 20130121-124640.gz
4667.Apple Error Text.txt
Same error ... different error?
Tags related ... crashed whilst trying to populate the library menu where you specify all resources or collection or tags etc.
5126.Apple Error Report.txt
1565.LogosLogs Martin 20130121-141333.gz
There are many Exceptions whilst syncing, but no crash logs nor logos.log to give context to the errors.
Initiate logging as per http://wiki.logos.com/Diagnostic_Logging#Logos_5_for_OS_X
[:$] Ooops ... forgot to set logging going again when I did the fresh install last month ... [:$]
It is on now ...
Thanks Dave.
As you probably realised, the logs were from 5.0b Beta 1 much earlier in the month.
Has this crash occurred again (now that logging is enabled)?
Not yet ... but then I have not done as much tagging in the last couple of days ... Thanks for the enquiry though ... I'll post again should it happen again ... but with better logs this time!
Regards
Martin.
Another crash that may be from extended tagging. I have been tagging quite a bit over the last 24 hours, when opportunity affords. Last night I closed the lid on my MBP as normal. On opening the lid and logging on to the MBP, I saw the Apple Crash report.
I have reported it here but it may have nothing to do with the tagging ...
Many Thanks
3716.Apple Error Report.txt
3463.LogosLogs Martin 20130201-071040.gz
I have reported it here but it may have nothing to do with the tagging ..
Correct. It was trying to rebuild the Library Catalog index from a metadata update. If Logos is now running normally then it has successfully rebuilt the index.
