[View:http://community.logos.com/cfs-file.ashx/__key/CommunityServer.Discussions.Components.Files/75/2677.Logos4.log.zip:550:0
]I've had a couple of crashes on A21 when I haven't been doing anything. I will be working in another app and A21 just goes away.
Log file attached.0184.Indexer.log
4336.Logos4.log.zip
[I] Recommend changing forum display name http://wiki.logos.com/Changing_Forum_Display_Name
Forum http://community.logos.com/forums/t/6731.aspx has log posting tutorial - step 1 already done.
For crashes, console messages usually helpful.
Posted Logos4.log and Indexer.log files appear mundane (i.e. no crashes).
Keep Smiling [:)]
Attached Console Log.
5241.Console Messages.log
Noticed "Out of Memory" message in console log = Logos crash.
Wonder how much memory installed ? Apple => "About This Mac"
Also wonder about free space on Startup Disk ?
Activity Monitor utility can show memory usage:
If Page outs > 0, then more memory requested than available (written to startup disk).
Your computer looks a lot like mine. MacBook Pro i7 with 8GB RAM. Start-up disk has 390GB available. I have been monitoring the CPU utilization pretty regularly, but haven't watched memory as closely. Currently page-outs show 266MB (hasn't been rebooted since crash).
P.S. I'm always smiling when I'm studying the Bible.
[:D]
[I] After installing 8 GB RAM, found enabling 64 bit kernel in Snow Leopard improved responsiveness. Personally used nvram example from:
http://macperformanceguide.com/SnowLeopard-64bit.html
[quote]
... Currently page-outs show 266MB (hasn't been rebooted since crash).
Restart should reset Page outs to 0 bytes. Spinning beach ball shows during Page outs (and other disk intensive activities).
Seems like I am still having an issue - but it is crashing more quickly now. I have attached logs and snapshots of memory usage.
Why would Logos be starting with <200M of RAM and then ballooning to 1.3G?
0385.Logos crash 6_20.zip
Seems like I am still having an issue - but it is crashing more quickly now. I have attached logs and snapshots of memory usage. Why would Logos be starting with <200M of RAM and then ballooning to 1.3G? 0385.Logos crash 6_20.zip
Can you try to update to 22.1 through the link in the release notes for that update? Tell us if that changes anything.
I've seen this in A22, A22.1 and now A23. The sync indicator just spins and spins and spins... The only way I can get it to stop is to change my preferences to NOT use the Internet and restart the program. Then my program is much more responsive. When I change the preference to use the Internet it goes back to spinning and spinning.
Also, I notice my memory leak is much faster when I connect to the Internet (that is how I noticed the difference). When I had my computer in Sunday School (no Internet connection) and told it to work offline the program was stable and stayed up for over 24 hours.
Right now when I am at home and online the program won't stay up for more than 60 minutes before it crashes. When I posted log files earlier, I was told I had run out of memory, but I have 8 GB of ram on my MBP i7.
Seems there is some sort of infinite loop in the sync process with my setup.
Please let me know if you would like me to capture specific information on this. I've posted info on the following thread:
http://community.logos.com/forums/p/18365/138280.aspx#138280
Thanks,
Chris
With A23 closed, wonder about moving your Library/Application Support/Logos4/Documents/v6fusczl.ehc/LayoutManager/layouts.db file elsewhere (perhaps trash), then opening A23 ?
If Sync Layout & Delete loop repeats, please post A23 console messages, logos4.log, and indexer.log files.
Apologies - had missed repetitive Sync Layouts and Delete cycles in console messages - Changed count always 33.
Chris:
Could you Open Logos4, turn "use internet" off in your preferences panel, open "Dictionary of Biblical Languages with Semantic Domains: Greek (New Testament) and scroll through it a bit, then turn "use internet" back on. Then type "rebuild index" in your command bar. and tell us if it crashes again with the new logs if it crashes.
