Stacer icon indicating copy to clipboard operation
Stacer copied to clipboard

Extrememy High Memory Usage (2GB+)

Open douglasg14b opened this issue 6 years ago • 7 comments

If stacer is open for a week or so, the memory usage balloons out to 2GB+ which is pretty extreme considering what it does....

douglasg14b avatar Aug 24 '18 19:08 douglasg14b

Hi @douglasg14b, Thanks for the warning. I will try to fix it in the new version.

oguzhaninan avatar Aug 26 '18 16:08 oguzhaninan

Could you allow Stacer to run a week again? But this time using Valgrind and posting ur logs after those 7 days?? Here's a guide, if you're down. 😀

http://www.valgrind.org/docs/manual/quick-start.html#quick-start.prepare

m-flak avatar Nov 22 '18 14:11 m-flak

@m-flak I will when I can install on ubuntu 18.10. Just upgraded with a new build.

Send me a reminder if I don't look back at this again once stacer is released for 18.10.

douglasg14b avatar Dec 07 '18 04:12 douglasg14b

The memory leak fix is currently only in the git upstream build. You'll have to compile from source in the meantime.

m-flak avatar Dec 30 '18 23:12 m-flak

I'm actually experiencing this issue also. Should users uninstall their current version and reinstall from source?

BlackArbsCEO avatar Jun 10 '19 00:06 BlackArbsCEO

I can't see a memory leak in 1.1.0, running since 5 days. Oh well, I can see memory usage of 1-1,5 GB of memory....

alexmyczko avatar Dec 16 '19 12:12 alexmyczko

This is 2022 calling.

v1.1.0 of Stacer was using 1.5 GB after being up for four days. It starts off using about 150 MiB according to Stacer's Processes pane.

This is not a huge issue as one can simply restart Stacer and I do have 16 GB of RAM.

johnblommers avatar May 03 '22 02:05 johnblommers