I currently have two windows open in Logos, and here is my Task Manager:
It is currently up to 5928.2MB since taking this screenshot.
You didn't indicate if indexing?
It is not indexing currently.
Here is my latest Task Manager:
Once it hits 9 Gigs, it begins to lag so I restart back to roughly 1000MB, then it starts climbing again. It only started doing this recently.
Also, the CPU is the first column. When Logos is indexing, the CPU usage goes up. In both screenshots, it's sitting at 0% and 0.2%.
Duh for me!
No worries at all. I'm just trying to find a solution. Right now, I have rebooted my PC and I restart my computer every hour. I'm a former programmer, so there are things to get around it for now, but I hope this isn't normal behavior. I have owned Logos for many years.
There may be a memory link but do you have any complex visual filters across broad swaths Scripture. I find that send my memory use up although not to the extent you show.
No filters or messing with filters. I just had 2 windows up, my sermon and a Bible—no searches or anything else. I have more when I'm studying, but I'm writing, so I simplify.
Thank you for the report. We've received a couple like this recently and are doing some investigation to see if we can find a cause.
Following, because I am experiencing a similar problem. Logos gets progressively laggier after restart until it becomes unusable…
Help! Logos 41.0 Extremely Laggy! — Logos Community
Yeah, this keeps persisting for me. I close all my windows except the Bible and the sermon editor and I work until it starts to lag. My new favorite friend is, "Pick Up Where I Left Off" on the home screen.
You ask: "Is it possible there is a memory leak"?
Yeah, lots of things leak as people get older and, apparently, software is no different!😂
If you have been experiencing higher than expected memory usage over time with Logos, can you please try entering the following command in the command box and selecting the corresponding option: set accessibility to no
set accessibility to no
You will then need to restart the application. Please report back if this seems to eliminate the problem or improve the situation.
I had a problem like this with one of the updates (can't remember with one) . I decided to delete all indexes and re-index the entire library i have. Ugh — took FOREVER to complete. But once done it stopped and has been behaving well.
Caution- the amount of time to rebuild all indexes is painfully long. Don't try without making sure you wont need access for an extended time. I have 23K books and it took a full day. In thinking about it, it makes sense that some index was trashed, but still existed. The memory may have been stuck without writing a repaired index. Logos' tools for users is limited, so whatever you attempt make a backup of everything before attempting. All of the searches use several indexes in the C,D,F of the task viewer. I could not tell which it was, just was stuck and unable to apparently write an updated index file. You can see this if you expand the logos.exe running in the task manager ( the number 6 shows the number of sub tasks running.
Wow. Something must be really going wrong on your computer. Maybe memory usage/corruption is slowing down the indexing? Unless it's a very old computer or very constrained in memory, or not using a solid state disk for example, that's REALLY slow. Some other app or malware may be hogging things, I assume you have checked to see what processes are consuming CPU and memory besides Logos? ? No way it should be that slow with modern Logos! I have a Macbook Pro, I can rebuild the entire index in 45-60 minutes tops - and I have 38,000 resources.
I'm happy to report that after 6 weeks, I was able to use the Sermon Builder tonight with no freezing.
I would assume that you run Logos on an SSD, whereas Terry's experience is fully consistent with using a spinning HDD drive.
Yep - I suggested that. I suspect the rest of the hardware is commensurate with having a non-SSD drive, which means multiple factors may contribute to a slow experience indexing; also, it's a computer not in compliance with the minimum recommended hardware for running Logos. I only replied because his advice "Don't try without making sure you wont need access for an extended time." is misleading for a computer matching the minimum recommendations, and someone reading the post may not realize that.
https://support.logos.com/hc/en-us/articles/360007554992-Recommended-Hardware-and-Software-for-Logos
Unfortunately, the cost of upgrades may prohibit some users from using a SSD. Many churches are running older H/W and even older O/S. Some are light years behind. Microsoft is not the same type of company as Apple. 'Nuff said about M$.
Unfortunately, it becomes a matter of absolute dollars spent and where. Some users are also on fixed incomes.
I have now upgraded to TWO SSDs, one small one for the swap file and one for general use.
Of course things run better now. My point was trying to help someone who may be in the slow boat category and just warning incase they started and were not prepared for a long duration of watching the hard drive light blink. I did not mean to mislead, merely caution about unexpected consequences. In short, "your milage may vary" is a unfortunate reality.
The comment from Andrew Batishko on April 25 seems to have fixed my issue for now. Thank-you!
