search

supermemo / SuperMemoAssistant

A companion app for SuperMemo 17-18 which extends its functionalities through plugins.
https://www.supermemo.wiki/sma/
MIT License
198 stars 21 forks source link

SMA high memory usage #128

Open dumbyme opened 4 years ago

dumbyme commented 4 years ago

SMA seems to be hogging memory over other applications.

Observations: 1) Windows Task Manager : SMA has over a GB memory for a tool that is "idle" (to the user). This is in comparison to Chrome with 20 tabs (and other extensions running - shows 32 processes for chrome) 2) Firefox with 33 tabs uses just about 500mb ram. 3) Visual Studio code with bunch of files takes up measly 200mb.

SMA-task-manager

SMA-task-manager-details

I have also attached memory usage file VMMap (using https://docs.microsoft.com/en-us/sysinternals/downloads/vmmap). The screenshot below shows - private bytes used by SMA.

SMA-high-usage-private-bytes

Below is a zip file of the .mmp file (use the VMMap to open the file) SuperMemoAssistant.zip

I am not an expert on memory leaks. As and end user, I would expect a process that is idle/listening mode to be a light weight process. System config - Windows 10, 32GB RAM + i7 Processor

dumbyme commented 4 years ago

It would be good to have others share their memory usage as well.

alexis- commented 4 years ago

Does your SMA start with a lower memory usage footprint ?

Zelss commented 4 years ago

here is mine.

Capture

nikedinikedi commented 4 years ago

image

image

Svennerin commented 4 years ago

image This is how it looks on startup. Memory use doesn't seem to change much overtime for me either.

dumbyme commented 4 years ago

Does your SMA start with a lower memory usage footprint ? @alexis - SMA starts with 360MB RAM and spikes to 1000MB+. the good news is that I have not observed any further memory usage. I was more concerned if SMA uses up all the private memory - in particular with low memory/resources machines. my current laptop has 32GB RAM and can tolerate spikes if any.

everyone. Thank you for taking time to share screenshots. I will make this issue as a low priority, not to be reviewed in any near release, revisit if anyone else (other than me reports). If there are no further reports by second release of open beta, we can close this.