Upgrade to L5 Crashing
I had hoped upgrading to L5 would have shown the performance improvements that others are reporting.
However, after download and indexing, L5 locked up and I had to force quit. Reopened and after opening timeline, L5 crashed. Scrolling is very poor.
So all in all, I'm guessing there is a problem with my installation.
These issues were increasing over the last few weeks with L4. Could there be a bug that was carried over to L5?
I've posted logs from same folder as I did with L4, so please advise if I need to do something different with my logs.2746.Archive.zip
Comments
-
Your logs show a confusing mix and it seems you are still running Logos 4 and there is no log for Logos 5 application. You should:
- Check if the Logos 4 application is still in your /Applications folder (it will be). If so drag the Logos 4 application to the trash and empty trash.
- Delete all the Logos4 logs from your logging folder /Users/PastorsBrain/Library/Application Support/Logos4/Data/uqlh0z84.iuh/Logging/
- Reboot your Mac (just to be sure)
- Check Wiki for how to check/set logging on for Logos 5, and turn it on if it isn't set
- Start Logos 5 - make sure there is not any indexing still happening
- In Command box type 'Update Now' and execute it, see if it reports anything to download
- If no more indexing, nothing to download start using Logos 5
- If Logos 5 crashes, wait for a while, do NOT restart it, then re-post your logs here
BTW notice you are running Snow Leopard on your mid-2010 MacBook Pro 15", you should consider upgrading to at least Lion. Of course that is just by way of suggestion, your machine can run (Mountain) Lion and there are benefits with it.
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
0 -
Thanks Patrick,
Followed all your steps:
1. Logos 4 was already in trash, only Logos 5 in Applications folder
2. Deleted old logs
3. & 4. rebooted & turned on L5 logging
5. No indexing started on its own. Indexing was completed after installing upgrade.
6. No updates available
7. opened L5 and tried to duplicate crash. Opened timeline and started scrolling around and sure enough, L5 crashed.
8. Logs posted.
(I will be upgrading to Mountain Lion soon.)
0 -
Michael Lane said:
8. Logs posted.
Suggest contacting Logos Technical Support => http://www.logos.com/contact
Found a thread with similar crash issues in a different application => http://www.cocoabuilder.com/archive/cocoa/277887-nsrecursivelock-problems.html that notes this crash occurs every 30K strings or so.
Logos.log file shows application recovered the first Recursive Lock, but crashed on the second time. The process number of 448 shows Mac OS 10.6.8 was recently restarted.
Keep Smiling [:)]
0 -
Anybody from Logos able to look at my logs?
0 -
I replied to you here: http://community.logos.com/forums/t/62187.aspx
In the future can we keep Threads on the same problem/topic in one thread? Also, it looks like tech was under the impression that you were going to call back if the behavior returned. If my advice in the peviously linked thread does not fix it, please call back. Let me know if you need your case number again, I can email it to you.
0
