Was typing a book title with Logos 5 crashed. Running OSX 10.8.2 and L5 SR-4. Attached are my logs.
1452.LogosLogs Donovan Palmer 20121121-205345.gz
Basically, there are too many open files! What that has to do with "Anaytical Key to the Old Te" I can only guess. What happens if you type it correctly?
Too many resource tabs in your layout? Do you have a collection with a large number of resources that is ticked for Parallel Resources?
I believe I only had about six resources open. I am generally one not to open too many at once because it gets too cluttered and confusing. I have a few workspaces that push this a bit, but I was not using one of them at the time.
Just retried the same action using the exact same text with the typo and it is fine now. I hope the crash log can help the developers figure out this mystery!
I have a few workspaces that push this a bit, but I was not using one of them at the time.
What about collections ticked for Parallel Resources?
Quite minimal. In fact, I was primarily looking at monographs.
I do have a growing theory... I have voiced this before. I have wondered how the 'state' of Logos is preserved when I put my macbook to sleep. My Bible programs are often open all day and when I am moving, or need to step away when I am on battery power, I will close the lid. I have a growing impression that Logos doesn't like this in terms of it's memory management. I could be off of my head, but it appears when it is running, connected to the internet and never put into sleep with the rest of my programs, it tends to run better. It has made me wonder if any of the development testing in the lab is ever done on laptops in scenarios that would be similar to portable computing on the move. What happens while it is sleeping and what does it need to 'catch up' on when it wakes back up? What happens if the IP address has changed or there is no connection at all?
I am going to try for a season shutting down Logos any time I need to put my macbook to sleep. This is a pain in that it won't leverage the instant computing part of the sleep feature, but if I find I have less trouble with Logos crashing, it might be a clue.
What happens while it is sleeping and what does it need to 'catch up' on when it wakes back up? What happens if the IP address has changed or there is no connection at all?
My experience of sleeping and waking Logos has been very positive, even when it awoke with no internet. It detects network availability and when it is idle, and smoothly resumes when woken e.g.
2012-11-22 12:03:09.4658 1 Info PanelViewModel Got panel settings for Bookmark: ...2012-11-22 12:03:09.4698 1 Info MainWindow MainWindow activated.2012-11-22 12:03:09.4698 1 Info PanelViewModel Got panel settings for Snapshot:...2012-11-22 12:08:09.4830 1 Info LDLS4.AppModel App is now idle.2012-11-22 12:13:22.9459 26 Info OurApp Network availability changed to False.2012-11-22 13:54:57.5100 18 Info SyncManager (Timed) Downloading items.2012-11-22 13:54:59.4681 35 Info OurApp Network availability changed to True.2012-11-22 13:55:05.0994 18 Info SyncManager (7581ms) Downloading items.2012-11-22 13:59:08.7973 1 Info MainWindow MainWindow activated.2012-11-22 13:59:08.8023 1 Info LDLS4.AppModel App is no longer idle.2012-11-22 13:59:08.8023 18 Info SyncManager (Timed) Downloading items.
It does look like the same crashes I was getting last week, Dave's suggestion re looking at Collections did the job for me — I found an old collection based on rating:>=0 that I never actually used and deleting that did the trick...
Well, it could be something completely unrelated to sleeping. Sometimes I am grasping at straws when Logos is the only piece of software on my computer that crashes regularly. Thanks for the suggestion as well to look at the collections.
Well, it could be something completely unrelated to sleeping.
Dave reported no problem with sleep, but he is a Windows user. Haven't used my MBP in a couple of weeks, but after it updates everything, will try your theory during the day today. Will give it a few cycles of open and close then see if I can make it crash. Will post my results back here.
Thanks Jack. I've not used the sleep function on my MBP and I haven't had any crashes, but I won't get too excited because I've not used Logos extensively today and I don't experience crashes every day. I'm going to not use sleep with Logos and if in a few weeks I have experienced no crashes, I'll back to my old pattern to see if they return.
There's nothing to lose here, except it takes a bit more time to load up and shut down Logos when I am on the move. Will report back over time what I experience.
I'm going to not use sleep with Logos and if in a few weeks I have experienced no crashes, I'll back to my old pattern to see if they return.
Opened and closed the lid a few times and then tried typing in the Library find field without incident.Anything else I should try?
I dunno. Our internet here is really challenging as you know. Today I left my laptop on all the time and connected to the internet. When I did go to close Logos, it hung on the saving settings thing in the end. After letting it do this for ten minutes, I did a force quit and it said that Logos was not responding so I forced it off and got a mac error report.
If many others (aside from documented bugs) are experiencing stability, I have to think it is my usage patterns such as sleeping frequently or the conditions here with patchy internet. I may experiment more with using it in the offline mode, but this being said on the plane the other day working in offline mode it crashed when I was doing something in the library window.
I'm going to keep experimenting to see if I can find the issue as it is the only piece of software I have issues with. If by the next time I get back to the States it is still insolvable, I may delete L5 completely and do a completely new install. I can't do it here as it would take 2,000 years to download it!
Thanks Jack for your help and happy thanksgiving!
One collection of Monographs can have several hundred resources and could be an issue if ticked for Parallel Resources! Untick it and see.
Ultimately this is related to Mono and the way it manages/disposes files, so is an issue for Tech Support to pursue.
Bump to make sure Logos has seen this and maybe would like to comment.
There is an open case for the 'Too many files open' crash. I will add a link to this thread to the case.
This issue should be fixed in 5.0b (RC1).
Oh, I'm glad to see that. Is there an ETA for that fix?
I tried to post a video of this kind of crash to the forum a few minutes ago, but it has to be moderated. Then I saw this answer.
http://community.logos.com/forums/t/65766.aspx
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
