L5 Mac Less Stable Than L4?
For me L4 was pretty stable. But L5 has been very flaky. It crashes just sitting there, changing layouts, searching and more. I can't isolate a variable for the crashes. Any ideas where to look?
Comments
-
I have not noticed these problems. My Mac is pretty old and L5 has been both more stable and faster. I hope that you can track down what's up
Bob
0 -
Some of the recent crashes are similar to a problem I had last week, it runs into problems with "too many files open". In my case I had a Collection with all resources in it and deleting that fixed things... (It would trigger crashes at seemingly random times i think it was doing stuff to populate the parallel resources menu in the background)
0 -
Dave - Looking at your logs from my not-quite-techie background, I did notice many "error" messages, many of which did have the "too many open files" warning that Jon mentioned. Have you tried opening to a blank layout (press and hold the command key immediately upon starting the app… check the appropriate box) and building a new layout? I think Jon might be on the right track. [Y]
macOS, iOS & iPadOS |Logs| Install
Choose Truth Over Tribe | Become a Joyful Outsider!0 -
Personally, I am finding L5 on the MAC very stable. I have only been using it for a few days, but I have had no crashes to date and the program seems much faster in many areas.
2015 13" MacBook Pro - 2 Ghz Intel i7 - 16 GB RAM - 500GB SSD - 2018 iMac Pro - 3.2GHz 8-core Xeon - both systems running OS 10.14.3 (Mojave)
0 -
I have had more crashes compared to L4 across different areas. Definitely more crashes. I haven't started investigating yet, wondering if due to resources. The only layout I am using I have created from scratch.
I don't want to run with logging enabled but if it continues I will have to to dig into it.
I did an in-place upgrade over Logos 4.
"I want to know all God's thoughts; the rest are just details." - Albert Einstein
0 -
Patrick S. said:
I don't want to run with logging enabled but if it continues I will have to to dig into it.
Have not noticed any difference in operation between logging enabled and disabled in L5 Mac. Tested this because I thought logging might slow L5, but it does not appear to have affected anything.
0 -
It would be great if Logos would create a better way to troubleshoot crashes. With as much data as these programs handle I imagine it's easy for a database or something to corrupt.
A crash because "too many open files" seems like an odd error. I'm running on a maxed out MBPr (may day job is video production).
Anyway deleting all my layouts and starting from scratch seems to have helped.
0 -
Dave Smith said:
A crash because "too many open files" seems like an odd error. I'm running on a maxed out MBPr (may day job is video production).
I've seen this as well in relation to my use of Logos on my MBP. I think there is some memory management issue where Logos thinks that there are too many open files. I rarely open more than eight or nine resources and usually it is less simply because a 15" screen is not that conducive to it. If I had a huge screen, I might be tempted to open many more, but opening lots of files is simply not something I do.
It may be in relation to my habit of putting my MBP in sleep mode and as a result rarely rebooting. I am changing my usage habits to always shut Logos down when I am on the move and to once a day do a complete restart. If I can see some improvement in the problem, I might be able to start to narrow down what is making Logos think this.
0 -
Dave Smith said:
For me L4 was pretty stable. But L5 has been very flaky. It crashes just sitting there, changing layouts, searching and more. I can't isolate a variable for the crashes. Any ideas where to look?
Looking in Logos.log noticed error: Unhandled exception in asynchronous work. ---> System.IO.IOException: Too many open files
If work offline, then would not have asynchronous work. Also noted a number of name resolution failures while syncing. Curious about network stability ?
Keep Smiling [:)]
0
