We upgraded one of the computers to ML (from 10.7 to 10.8). ML is very nice in L5 we are actually receiving less spinning wheels now while scrolling - considerably less. However, we still have the BSL crashing. Hopefully development will have a solution soon, if not back to BW, or possibly try Acordance.
Yours In Christ
5 Solas:However, we still have the BSL crashing.
Curious about word(s) in Bible Sense Lexicon that crash ? Please elaborate how to repeat crash.
Apologies: using Logos 5.0b Beta 1 on OS X 10.8.2 in full screen mode currently am not crashing. Started with a blank layout by using close all command, then opened Bible Sense Lexicon and opened two Bible Word Studies:
Caveat: noticed Logos 5.0b Beta 1 is a bit buggy for changing Bible Sense Lexicon focus since clicking on diagram needs improvement.
Keep Smiling
Logos Wiki Logos 7 Beta Free Support
Thanks for the reply. Mine will not even open. I select it. Wait 15 or seconds and L5 closes. It gives me an error report. This happens on two different Macs - mini and MBP - both only a year old ... The same thing happens when using the Community group settings in tools too. Spoke with Apple. They looked at the systems. Everything is running fine. They looked at the crash logs and stated it is a software issue. I am suppose to have a solution by Monday - hopefully - from Logos.
Confirmed. I just got a Macbook Pro Retina 13" (running Mac OSX Mountain Lion 10.8.2 and Logos 5.0a SR-3) and Logos crashed as soon as I clicked on the Bible Sense Lexicon. So far, it has only happened the first time.
Logos 9 | Faithlife Connect Essentials27" Win10 (21H2) AMD FX-8350 (4GHz) 16GB DDR3 2x500SSD 1x240SSD 2x3TBHDDrMBP13" macOS 10.15.7 i7 (2.9GHz) 8GB DDR3 512SSDiPadPro (2020) iPadOS 15.1 | iPhoneXR iOS 15.1
Wow. I just tried BSL and mine crashed too. First the spinning color wheel and then ... nothing (L5 closed down). Hmm.
Sure a fix is on the way; till then I'll steer clear.
Normal.dotm 0 0 1 132 753 IIIM 6 1 924 12.0 0 false 18 pt 18 pt 0 0 false false false
Since I had not heard back from Logos Tech Support (understandable, they are busy), I e-mailed them on Friday. Here is part of the reply on this issue:
___
We have not received any information back from our developers on this issue at this time.
I'd recommend you give us a call at 1-800-875-6467 on Monday to check up on this but it's not likely we'll have a fix for this by then.
The root of the issue is how the new version of Cocoa (a Mac programming platform we use) handles memory. This is a complex fix and will take some time.
I will call them on Monday to see how long this needed fix will take. I will also try to find out if there is a temporary work around on this issue … (besides not using it).
I must admit I am somewhat saddened and disappointed that Logos is releasing and marketing these so-called "upgrades" when in reality some of them are not fully functional and others do not even work. I know Logos is working hard and I appreciate it (we need these programs, appreciate their commitment, et. al), but IMO they continue to release programs, upgrades, etc. "to early."
5 Solas: ... I know Logos is working hard and I appreciate it (we need these programs, appreciate their commitment, et. al), but IMO they continue to release programs, upgrades, etc. "to early."
... I know Logos is working hard and I appreciate it (we need these programs, appreciate their commitment, et. al), but IMO they continue to release programs, upgrades, etc. "to early."
Likewise appreciate awesome improvements. Logos has a release early and often strategy, which does incorporate customer feedback. Some issues are resolved sooner than others.
After experiencing a number of crashes with Too Many Open Files in Logos 5.0b Beta 1 on OS X 10.8.2, personally using a work around on a Mac with 16 GB of RAM. Caveat: initial work around attempts increased crash frequency.
We are already running the maximum RAM in both of our Macs (new in 11/11) - 8 RAM ... The Logos website recommends 2-6. So, either the website is incorrect, or it is not necessarily the amount of RAM (if one is running the recommended or above), but the present lack of programming that controls how Logos uses memory, etc. If I am not mistaken (or mis-phrasing what a friend told me) this is 'in part' what the programming in cocoa is for - memory management ... for Mac users. Window users are having memory problems to ... similar issue, different programming ...
5 Solas:We are already running the maximum RAM in both of our Macs (new in 11/11) - 8 RAM ... The Logos website recommends 2-6.
Logos 4 and Logos 5 are 32 bit applications. For running Logos, 4 GB Ram is a realistic minimum.
Logos 4 and Logos 5 share a core set of .NET Framework code. On OS X, mono provides .NET Framework capabilities. The user interface code is different for Windows and OS X.
Apple has defaults for the number of maximum files that can be opened by the OS X kernel. OS X 10.8.2 ships with a default limit of 12,288 open files, which is lower than a number of open source distributions.
5 Solas:PS: While it would be useless to have a library and have no resources open for study, just so we could use BSL, we tried that too - it still crashes.
Logos 5.0b Beta 1 added graphical display for Bible Sense Lexicon. Crash issues in stable releases receive high priority for Logos development; wiki shows a number of service releases that were released one day later => http://wiki.logos.com/Mac_Release_Notes_and_History
Logos is still researching the problems. They have been on my computer for hours - still on it. It may not be a memory problem as first suspected. They are looking at the possibility of a corrupt book(s), etc. One thing for sure- they are working hard to try to give us a resolution. If we - rather they - discover the solution we will of course post it what worked here ...
Not repaired, but hopeful.
Logos was able to duplicate the same crash on another machine - using the same books I have open, et. al. So, at least it was replicated on another computer ... which gives them an avenue to locate the problem. ...