Logos takes forever to load
I've always had a problem with Logos taking forever to load, and it happens on all of my computers. I'm using it regularly on 3 different computers. They're all running Windows 11. I just timed it on my main laptop, and it took 1 minute 32 seconds. That was not abnormal. It is on an NVMe drive, so that's not the issue. And I don't have very many tabs open. 3 Bibles and 3 dictionaries. That's all. It's just annoying that it takes that long to load.
Anyway, I'm not here just to complain. Haha. I was wondering if anyone has any tips on what might speed up the loading of the program?
Comments
-
JDC said:
I've always had a problem with Logos taking forever to load, and it happens on all of my computers. I'm using it regularly on 3 different computers. They're all running Windows 11. I just timed it on my main laptop, and it took 1 minute 32 seconds. That was not abnormal. It is on an NVMe drive, so that's not the issue. And I don't have very many tabs open. 3 Bibles and 3 dictionaries. That's all. It's just annoying that it takes that long to load.
Anyway, I'm not here just to complain. Haha. I was wondering if anyone has any tips on what might speed up the loading of the program?
That is very unusual for a modern laptop with an NVMe. Can you enable logs and upload them here? There are instructions on the wiki: https://wiki.logos.com/Diagnostic_Logging
But the easiest thing to do is hold down CTRL while you open Logos. Then find them at %LocalAppData%\Faithlife\Logs\Logos zip them and upload them here.Using Logos as a pastor, seminary professor, and Tyndale author
0 -
Thanks for the quick reply. I'll attach a zip file with the logs. Even doing that and loading to a blank screen took over a minute.
Thanks for your help!4861.JDC Logs.zip
0 -
Turn off your internet and try to load it. Someone a few weeks back raised the same issue. It appears Logos is very internet demanding on startup. Their internet was very slow and this caused the problem.
1 -
I tried that a while back, and it did help slightly. I have fairly fast internet, though, and I don't usually have any problems on that end. Plus, I found that as soon as I turned off the internet, I could no longer do fuzzy searches. So it's just not worth it to have that off. I was hoping maybe something else might come up to help matters.
0 -
-
I don't see any single thing in your logs that is taking a lot of time. Everything is just taking a long time individually. But your CEF is showing a DNS error. Can you try booting Windows in safe mode? It might be a conflict with your Antivirus? Adaware in particular is known to cause problems.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
I only have 3 Bibles: NASB, NIV, and KJV, plus the Complete Word Study Dictionary: New Testament. Those are my only resources. When I ran the log files, it loaded to a blank layout, and still took over a minute. Pretty crazy.
0 -
I loaded Logos from Safe Mode, and it loaded to a blank layout. It only took 27 seconds, which is quite a bit better. I'm not even using any antivirus, other than the built-in Windows Defender, or whatever it is called. Do you have any ideas on that?
And thanks for your help, guys.
0 -
JDC said:
I loaded Logos from Safe Mode, and it loaded to a blank layout. It only took 27 seconds, which is quite a bit better. I'm not even using any antivirus, other than the built-in Windows Defender, or whatever it is called. Do you have any ideas on that?
And thanks for your help, guys.
If Safe Mode made such a big difference, there is something else on your computer that is fighting with Logos. Other than antivirus, I am not sure what it could be. Hopefully, someone else will chime in with a solution, but if not I will spend some more time doing some research.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
I just tried turning off the internet features to see what kind of difference it would make. It still took 1 minute 10 seconds to load. So it's definitely not worth it for me to turn that off.
0 -
JDC said:
I loaded Logos from Safe Mode, and it loaded to a blank layout. It only took 27 seconds,
From the log, your normal startup took 55.1s (to a blank layout). A log from Safe Mode would provide a comparison, but switch your antivirus off in Normal mode to see if that improves matters.
Dave
===Windows 11 & Android 13
0 -
JDC said:
I loaded Logos from Safe Mode, and it loaded to a blank layout. It only took 27 seconds, which is quite a bit better. I'm not even using any antivirus, other than the built-in Windows Defender, or whatever it is called. Do you have any ideas on that?
Here's the first line from your log file:
Logos.log said:2024-09-06 17:22:25.7859 INFO 1 OurApp | Starting application (36.0, version 36.0.0.0733 x64 on Microsoft Windows NT 10.0.22631.0, .NET 8.0.7) at 17.123 seconds.
For comparison, here's mine:
Logos.log said:2024-09-08 18:56:33.3443 INFO 1 OurApp | Starting application (36.0, version 36.0.0.0733 x64 on Microsoft Windows NT 10.0.19045.0, .NET 8.0.8) at 0.675 seconds.
Virtually no Logos application code has run at this point, just enough to initialize the application and create the log file. This indicates to me that something else on your system is interfering with Logos and dramatically slowing it down, but I'm not sure what.
Can you add Logos' program and data folders to Windows Defender's exclusion list for on-access scanning? Perhaps that might help.
0 -
Before I tried this, I closed my tabs for Search and for copying Bible verses, and I had already added an exception to the Windows Firewall for Logos. Doing those things got my load time to around a minute. After doing what you suggested, I added an exception for the Logos folder in Windows Defender, and it still took 55 seconds to load. I don't have any other antivirus software, or anything like that. I wonder what in the world it could be. Do you have any ideas what else could possibly cause this?
One thing of interest is that it takes the same amount of time on all of my computers. I'm running Logos 10, and I paid for the Logos 10 full feature upgrade. But my library (other than the books I've bought more recently) is from Logos 6. That shouldn't cause any issues, right?
0 -
-
What kind of CPU do you have? That might make an impact. Also have you optimized your drive lately? You might have a bad RAM chip (very very unlikely) that is slowing you down.
I know when I upgraded from a Ryzen 1600X to a 3700X, I didn’t see a huge difference, but it did make a difference.
0 -
What kind of CPU do you have? That might make an impact. Also have you optimized your drive lately? You might have a bad RAM chip (very very unlikely) that is slowing you down.
I know when I upgraded from a Ryzen 1600X to a 3700X, I didn’t see a huge difference, but it did make a difference.
0 -
No, I've had Logos since version 6, and it has never run faster for me. It has always acted just like this from the beginning, no matter what computer I run it on.
And to answer Ezra, I've run it on several different computers, and it's always been slow. The laptop I've been testing and posting from isn't a powerhouse, but it's not too awful. It has an Intel i5-1035G1 with 8GB of RAM. It is running off of a NVMe hard drive.
But I did just load it on my gaming computer, which has an i7-13700K, RTX 4080 (which shouldn't matter for loading), 32GB of DDR5-6000 RAM, and a PCIe Gen 4 NVMe drive. It loaded in 17 seconds, which seems lightning fast compared to a minute and a half. Haha. But you shouldn't have to have a beast like that just to run Logos.
0 -
A 10th gen i5 should work, but 8 GB of RAM is pretty low. The recommended system requirement is 16 GB. If it is not soldered, adding another stick of RAM would probably make a substantial difference.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
Justin Gatlin said:
A 10th gen i5 should work, but 8 GB of RAM is pretty low. The recommended system requirement is 16 GB. If it is not soldered, adding another stick of RAM would probably make a substantial difference.
Yeah, you're probably right. I tested the loading time on one of my other computers that does have 16GB, and it didn't take nearly as long as I remembered. It only took around 30 seconds. So I got to checking out my main laptop that has the problems. Not only does it only have 8GB, but the second hard drive that I thought was an NVMe drive is actually an HDD. So when I get a chance, I think I'm going to upgrade my RAM and also slap an NVMe drive in there and get rid of the HDD. I think that should probably help a lot.
Thanks for your help, everyone! When I get my laptop upgraded, I'll share the results.
0 -
-
Ok, everyone. Here is my update.
I originally had only 8GB of RAM and was running Logos off of an HDD. I threw in 32GB of RAM, got rid of the HDD and replaced it with a Gen 4 NVMe drive. In the beginning, I was complaining about it taking 1 minute and 30 seconds to load. And now...
18 seconds. Wow! That's a pretty crazy difference. I'm definitely happy with that relative to 1:32.
Thanks, everyone!
0 -
-
Could you post another log file? I'm still curious where that error message was coming from.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
Justin Gatlin said:
Could you post another log file? I'm still curious where that error message was coming from.
Sorry about taking so long. I've had a lot going on recently. But here are the log files from after I've upgraded and it's loading faster.
Thanks for checking into it.
0 -
The error is gone. I did a little research and found out that Windows will sometimes end the CEF process if you are low on RAM. I guess that is what was happening. Your RAM filled up, CEF closed, CEF opened - wash, rinse, repeat. With your antivirus off, your RAM probably had a little more breathing room and so it didn't go through as many iterations. Very interesting. I am glad the problem is solved.
Using Logos as a pastor, seminary professor, and Tyndale author
0 -
Justin Gatlin said:
The error is gone. I did a little research and found out that Windows will sometimes end the CEF process if you are low on RAM. I guess that is what was happening. Your RAM filled up, CEF closed, CEF opened - wash, rinse, repeat. With your antivirus off, your RAM probably had a little more breathing room and so it didn't go through as many iterations. Very interesting. I am glad the problem is solved.
I really appreciate your checking into this. That really is interesting. Seems like there should be some way they could work around a problem like that, though. 16GB of RAM minimum seems pretty steep for software like this. But it is what it is, and I'm glad it's working better for me now.
Thanks again!
0
