Slow increase of memory usage over time

[ownedbycats]

Question: Does anybody else (particularly those using Windows 10) have Calibre slowly increase in memory usage over time, but never go down until it's restarted?

I'm not sure if it's a bug with Calibre, Windows 10's notoriously poor handling of memory (I'm one of those affected by the standby memory glitch), or something specific to my configuration.

Thanks.

[BetterRed]

Nuh, just watched mine for a few minutes go up from 222.3MB in a couple of steps to 237.4MB. When I stopped doing anything it dropped back to 187.8MB (in secs rather than mins), then went up up 189.2 and sat there like a stunned mullet. Jumps up when I switch to a library with more books and custom columns.

I probably have fewer plugins: CalibreSpy, Count Pages, Drop Search Results, Extract ISBN, Favourites Menu. Find Duplicates, GetFileName, Job Spy, Modify ePub, View Manager

BR

[ownedbycats]

Just curious: have you ever noticed if you're affected by the standby memory bug? It's where the standby cache (it can be seen in the resource monitor and RAMMap) gradually fills up all of the free memory and then never releases. I have a scheduled task set to run every few minutes to manually clear it.

[BetterRed]

Don't even know what it is. What happens when it fills up.

Anyway here's mine right now



RAMMap roadblocks Snip and Snap

BR

[ownedbycats]

The glitch is known for causing stuttering in memory-intensive games. I think excessive swap file usage too. Standby is the dark blue section there - you might be affected too, if it never goes down.

[BetterRed]

Originally Posted by ownedbycats

The glitch is known for causing stuttering in memory-intensive games. I think excessive swap file usage too. Standby is the dark blue section there - you might be affected too, if it never goes down.

So I exited Firefox, and down it came, as I guessed it might



BR

[ownedbycats]

Good, it seems you're not affected by the bug. For those who are affected, the dark blue section never goes down unless manually cleared with RAMMap or Empty Standby List.

Originally Posted by BetterRed

RAMMap roadblocks Snip and Snap

BR

Greenshot also has trouble grabbing screenshots of elevated/admin-right windows unless I also load Greenshot as elevated.

[DNSB]

Interesting. On my system, the Device Locked item hits about 125MB at it's peak and drops back to under 50MB rather often. If I run VMWare WorkStation Pro and open multiple VMs, I start consuming memory like it was free and the Driver Locked goes to 123MB which is a pretty small chunk of the 23GB Task Manager shows as being used.

This is on my old laptop I'm using from home.

[ownedbycats]

The sneaky thing about standby memory is that task manager displays it as free. When it's working right, this is correct, but the glitch results in it never actually being released back to the pool of free memory.

From what I recall, it can happen when the OS or some buggy piece of software (drivers may be a culprit, though I keep mine up-to-date) just forgets that the temporary memory was allocated and re-allocates it, orphaning the old cache. It just remains in RAM indefinitely. Clearing it basically just flushes it out to swap so it can be properly discarded.

[ownedbycats]

Update: The issue seems to not be occurring anymore. I'm not sure if it's updating Calibre to 5.9, updating one of my plugins, or some change in my system configuration, but now an inactive Calibre will drop its memory usage.