I can't launch Logos 4. It crashes right after saying "logging in" but before saying "preparing your resources (or library)". I imagine it would work with a restart. But in the meantime, here is my log file.
8875.Archive.zip
Looks like I should have grouped this with the other group of emails that recently started crashing as well. I also tried removing the layout.db but that didn't help.
Robin
O.K. So I downloaded a new copy and tried that, to no avail. Same error. Then I restarted the machine and it let me in, (logged in and prepared my library) but the home page had no content. It crashed a few seconds later. When I tried it again, it was back to the usual error of logging in with no preparing library and instant crash. Here is the log.
0882.Archive.zip
Robin,
Do you run Logos 4 windows as well? Have you created a large number of documents? (Passage Lists, Reading Plans, Notes, etc)?
This could be a bug in our shared code when synching a large number of documents on Mac and creating too many files too quickly. I'll post a bug in our bug database and we'll take a look.
Hi Tom,
No, I don't run Logos 4 Windows as well. And I have not created a large number of anything in Logos in that this is my first year with it. I have one Bible reading plan, 0 notes, and I think 0 passage lists since I'm not even sure what those are. Hope that helps. So for the time being, I'm dead in the water since I can't start it up. I might consider uninstalling everything and then starting fresh unless you have any other ideas. Before, I didn't uninstall but rather just re-downloaded A17 and pasted it on top of itself.
Hello Tom,
I can't seem to get it to work still. I tried your post in the other thread of running the terminal with the particular line that you had to run the indexer, but still no go. Hmm. Here is a new log. I don't know if it helps or not.
4113.Archive.zip
Thanks for the update Robin,
I see in your logs there is a crash report here: /Users/rjparedez/Library/Logs/DiagnosticReports/Logos Bible Software 4_2010-04-15-222907_Home.crash
Could you post that log file to this thread? That might give us some more info.
Tom
I see lots of other programs in your console logs are crashing with similar errors of too many open files:
4/15/10 10:28:46 PM com.apple.launchd.peruser.502[121] (com.apple.ReportCrash[943]) Bug: launchd_core_logic.c:3672 (24003):9
4/15/10 10:28:46 PM com.apple.launchd.peruser.502[121] (com.apple.ReportCrash[943]) open("/dev/null", ...): Too many open files in system
Can you run the following from Terminal and let me know what the results are?
ulimit -a -H
Thank you Tom for your reply: Here are the results from running the ulimit-a-H
core file size (blocks, -c) unlimited
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
max locked memory (kbytes, -l) unlimited
max memory size (kbytes, -m) unlimited
open files (-n) 2000
pipe size (512 bytes, -p) 1
stack size (kbytes, -s) 65532
cpu time (seconds, -t) unlimited
max user processes (-u) 532
virtual memory (kbytes, -v) unlimited
As to the crash report. I went to that folder and found at least 5 crash reports for Logos. I compressed them all and put them in an archive that is attached here and I hope will help. I certainly hope that this isn't some issue with my machine that I am thus burdening your time with. I'm hoping that it may be an issue with Logos (which would make me feel better that it is somehow helping the stability of Logos). Thanks again,
There's your problem:
Our app uses a lot of concurrently open files while running and requires a lot more that 2000 at times. The default hard limit is unlimited and apparently something on your system is setting this to 2000. Once Logos 4 tries to open the 2001st file the system complains that the app is exceeding it's limit and it crashes.
I'm not sure where this is being set on your system, but the number needs to be increased. This can be done with the ulimit command from the Terminal or in one of your startup files.
From the terminal, you run the following commands in order to verify that this will fix the problem:
sudo ulimit -H -n unlimited
ulimit -H -a
/Applications/Logos\ Bible\ Software\ 4.app/Contents/MacOS/Logos\ Bible\ Software\ 4
I typed in the first command. It prompted me for my password saying to be careful with the sudo command. after providing it, I ran ulimit -H -a and it looked the same. Ie., it didn't increase it to more than 2000. Thus when I ran the last command, it crashed again.
Hmm. Is this something I need to call Apple for? I imagine your actual version beta or otherwise will still need to have open files set to more than 2000. The weird thing is that I haven't installed any new software in the last few months and have been using the alpha's successfully until A17.
Thanks for your help.
Hmm. Is this something I need to call Apple for? I imagine your actual version beta or otherwise will still need to have open files set to more than 2000.
Yes, if Apple can help you track down why ulimit for open files is being set to 2000, I would recommend it. Please keep us updated on what you find out.
The weird thing is that I haven't installed any new software in the last few months and have been using the alpha's successfully until A17.
You might be able to use the app if it didn't open more than 2000 files. It's hard to say when you hit that limit since we try to set the limit far beyond what we think we'd need so that the application doesn't crash in the manner you've experienced. The problem is that a single application is not allowed to override the hard limit set by the system, so our command to set the soft limit to 10240 won't override the 2000 hard limit on your system. (Sorry if that's a bit technical)
You asked me to keep you posted on this. The good news is that Logos is now running and working well. My open files are now back to unlimited as well. The bad news is that I had to wipe my whole computer to do so and reinstall from scratch. Apple didn't really want to find out why the limit was unchangeable. Instead they just had me start from scratch. I'm double checking everything now to see if I can find the cause if it shows up again.
Thanks again,
Available Now
Build your biblical library with a new trusted commentary or resource every month. Yours to keep forever.
