Logos Program Loading and Functioning Extremely Slow

For the last three days, Logos is taking and extended period to load and frequently displays the busy icon. Additionally, a minute or so after loading a dialogue pops up stating that "LogosCEF has stopped working".

After several minutes, the program populates the various layout windows and functions, albeit extremely slowly to the point it is almost unusable.

Software version 9.1.0.0018

Windows 10 Pro, Version 1703, OS Build 15063.2108

Find more posts tagged with

Desktop App

Comments

Dave Hooton

Try deleting the folder C:\Users\username\AppData\Local\Logos\Data\random-name\WebBrowser, otherwise upload your log files folder using the paperclip icon.

Robert Forlenza

https://community.logos.com/discussion/comment/1145762#Comment_1145762

I deleted the folder as suggested. That did not help or correct the situation. It is an extremely frustrating situation. I am attempting to prepare lessons and the software I depend on is nearly useless.

3051.Logos.zip

I have attached the log files.

Dave Hooton

https://community.logos.com/discussion/comment/1145776#Comment_1145776

Try deleting C:\Users\u0967771\AppData\Local\Logos\Data\u3dorypx.g1s\ResourceManager\Resources\WordSenses.lbswsd

and it will download a new Bible Senses.

Robert Forlenza

https://community.logos.com/discussion/comment/1145802#Comment_1145802

File was deleted. No discernible difference.

Robert Forlenza

https://community.logos.com/discussion/comment/1145852#Comment_1145852

This morning I attempted to uninstall the software and performed a reinstall. After nearly an hour, the same situation occurs.

Logos is fundamentally useless. It is extremely slow and frequently busy.

JT (alabama24)

https://community.logos.com/discussion/comment/1145865#Comment_1145865

I understand that you are frustrated. Hopefully this issue can be resolved for you soon.

After nearly an hour, the same situation occurs

A full reinstall and indexing would likely take longer than an hour unless your library is fairly small.

This morning I attempted to uninstall the software and performed a reinstall.

Deleting and reinstalling the app, by itself, is rarely a fix. Did you include all of the data files (which would manually need to be deleted)? As I mentioned above, that would likely take longer than an hour.

Dave is a full fledged techie, but I do have a suggestion. Have you tried loading to a blank layout? Press and hold the control key immediately upon startup. See if you can do some basic things and then slowly add some features back. It may be that a particular tool or search is causing troubles and this might help you to discover that issue.

Robert Forlenza

https://community.logos.com/discussion/comment/1145895#Comment_1145895

Yes, I understand that uninstall and reinstall generally does not resolve issues. Once in a while, I have been pleasantly surprised and had the time to try. Since there are no real troubleshooting schemes offered, I took a shot. I did the Uninstaller and then deleted the Logos folder from the Local App Data under the User folder.

Yes, I had uploaded the log files after starting a blank layout. I plan to do that again after giving the system/program the day to reindex. I have a rather large library and figured I would give it plenty of time to update, add resources and index.

Bradley Grainger (Logos)

Your log files do show that Logos is running pretty slowly, but don't indicate any particular cause.

What are your system specs? CPU, RAM, disk? SSD or HDD?

The version of Windows 10 you're running is almost 4 years old and is out of support; is there a reason you haven't updated to 20H1 or later?

Robert Forlenza

https://community.logos.com/discussion/comment/1145902#Comment_1145902

Not home at the moment to provide all specifications but the system ran perfectly fine, speedy, two weeks ago. The only changes have been any updated resources that were pulled in bulk Logos.

The system is a hp zBook , has 2 500gb SSD drives and 64gb ram. Windows has not been updated because it is a corporate unit and they control the updates. While I appreciate the importance of updating regularly and do so on my family's computers, they value stability and have locked down updates until they review and authorize them. That being noted, everything functioned with good speed until recently and there were no system changes in that period.

Dave Hooton

https://community.logos.com/discussion/comment/1145905#Comment_1145905

Windows has not been updated because it is a corporate unit and they control the updates.

Your version is still supported by Faithlife (for Logos), so I recommend you let Customer Service have a look at your computer (quote this thread).

Robert Forlenza

https://community.logos.com/discussion/comment/1145961#Comment_1145961

Correction to earlier post ...

My system is running on an Intel Core i7-6820HQ CPU @ 2.70 Ghz. It has 32.0 GB RAM and two 1 TB SSD drives. Logos is installed on the main SSD, C:, which is a 1.0 TB Crucial CT1050MX300SSD4. I do not believe that hardware is an issue but I am open to testing/troubleshooting.

The Logos Bible Software Indexer is currently using between 65% - 78% of the CPU with Logos closed. Hovering over the Logos icon in the taskbar states "Logos Bible Software is indexing (0% complete)". I rebooted the system about 45 minutes ago and opened Logos and closed it. When the software and the indexer were running, the Logos Bible Software Indexer was using 40%-65% of the CPU and Logos Bible Software is using between 8% and 30% of the CPU. The CPU is running at 99%.

Given the size of my library, I can see the indexing taking time but the fact that it is still at 0% has me wondering. Is there any way to evaluate a file to verify that the indexing is actually occurring?

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1145986#Comment_1145986

Is there any way to evaluate a file to verify that the indexing is actually occurring?

If logging is enabled (https://wiki.logos.com/Diagnostic_Logging) then %LOCALAPPDATA%\Faithlife\Logs\Logos\LogosIndexer.log will be periodically updated with progress (should be multiple times per minute under "normal" conditions).

Robert Forlenza

https://community.logos.com/discussion/comment/1145989#Comment_1145989

It took approximately thirty (30) hours for the indexing to complete. Operationally, the software remains extremely slow/practically unusable. I am attaching the latest log files.4377.Logos.zip

Ted Harms

https://community.logos.com/discussion/comment/1145762#Comment_1145762

Thanks Dave. I was not having any significant issues with slowness but this tip really improved my performance.

Dave Hooton

https://community.logos.com/discussion/comment/1146118#Comment_1146118

.4377.Logos.zip

What happened to the Logos Indexer log (not the error log)? No more CEF failures?

Robert Forlenza

https://community.logos.com/discussion/comment/1146178#Comment_1146178

Dave ... I was getting that early on when I was trying to use navigate in Logos while it was still working on loading as the screen populated. I have given up on that and just waited for the program to load. I haven't seen the LogosCEF issue since then.

The indexer was progressing, albeit it took longer than I ever anticipated. Since I saw it get to 99% and then finish, I did not include it. I questioned it because it was at zero for a while.

Robert Forlenza

https://community.logos.com/discussion/comment/1146215#Comment_1146215

This morning I attempted to capture additional information. I enabled full time logging.

I started the program. (All times are HH:MM:SS)

The splash screen appeared and disappeared at 00:00:13.

The synchronization screen then appeared, disappearing at 00:00:21.

The screen was then blank until 00:00:39 when the opening sound was heard.

A blank window, see below, opened at 00:05:50.

The screen slowly began to fill in, see below. Pet the Task Manager, Logos was using 40%-75% of the CPU during the filling in.

At 00:07:59 a "LogosCEF" error window appeared.

The window was fully populated, or at least appeared to be, at 00:11:43.

At this point, there was a single notification that Logos was "Preparing library" which remained until 00:12:50.

1680.Logos Logs.zip

Bradley Grainger (Logos)

https://community.logos.com/discussion/comment/1146232#Comment_1146232

This is definitely much slower performance than you should be experiencing with your system specs. Please capture a trace with the Windows Profiler Utility: https://wiki.logos.com/Logos_Windows_Profiler_Utility

NB.Mick

https://community.logos.com/discussion/comment/1146241#Comment_1146241

This is definitely much slower performance than you should be experiencing with your system specs.

Just a datapoint: in a parallel thread (unfortunately in German language) a user with a fast, recent system experienced incredible slowdown of Logos due to the Acronis Active Protection utility that tried to protect his machine from ransomware, but brought Logos - and other software, as it turned out - to a nearly complete stand-still.

Robert Forlenza

https://community.logos.com/discussion/comment/1146254#Comment_1146254

@NB.Mick Kudos and thank you so much!

I turned off Acronis Active Protection and Logos is again zipping through. I've been performing searches and changing layouts with essentially no wait time and my CPU usage fluctuating between 4%-25%.

Definitely something that could be helpful to others. Much appreciation to everyone who assisted and offered input.

NB.Mick

https://community.logos.com/discussion/comment/1146260#Comment_1146260

@NB.Mick Kudos and thank you so much!

Great to hear this was helpful and your Logos is working again!

Dave Hooton

https://community.logos.com/discussion/comment/1146254#Comment_1146254

a user with a fast, recent system experienced incredible slowdown of Logos due to the Acronis Active Protection utility that tried to protect his machine from ransomware, but brought Logos - and other software, as it turned out - to a nearly complete stand-still.

Very timely. I have a trial of Acronis 2021 but I turned off its security/protection utilities because I have a trusted one already doing active protection (and inherently distrust a known provider of one service suddenly including Security).