Insane (11GB) RAM usage, when using "code-time" plugin

[igoryonya]

Describe the bug
I've noticed a huge memory usage in Atom: 12GB of RAM
Thought, that maybe some, plugin is loading so much of RAM, becaue it used to be between 2 and 6 GB.
Ran in --safe mode and it used ~1GB.
At first, decided to test community plugins by turning off one by one and restarting Atom to see if it affected the RAM usage, but then found a manual about Atom profiling and found out about a TimeCop.
TimeCop didn't show a ram usage, but it showed a load time per package.
According to TimeCop, the "code-time" package takes the longest time to load.

Thought, that maybe it is related to a RAM usage somehow.
Disabled the plugin:

Restarted Atom and checked the RAM usage with "code-time" disabled:

It appears, that i nailed it. The memory usage has dropped by ~11GB.
Ran Atom for a while to see, if the RAM usage will start rising, but it didn't, so turned on the "code-time" back:

while monitoring the memory usage:

The RAM usage jumped up immediately without even a restart.

Desktop (please complete the following information):

• OS: Ubuntu 18.04.5 LTS (bionic) [Linux ws02800008006 4.15.0-118-generic #119-Ubuntu SMP Tue Sep 8 12:30:01 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux]
• Plugin version: 4.3.9
• Atom: 1.51.0
• Electron: 5.0.13
• Chrome: 73.0.3683.121
• Node: 12.0.0

Additional context
Atom is a flatpack package from flathub:

flatpak run io.atom.Atom

[xavluiz]

Hi,
We apologize for the memory issue and thank you for the issue update. We've cleaned up the plugin to optimize the code time functionality in v4.3.11. Please let us know if this helps. It's currently only running at a max of 110GB during testing but we'll continue to look through the code more to make it more efficient.
Regards.

[igoryonya]

Hi,
I updated and enabled, but no, unfortunately, it still munched on the RAM:

PS:
I disabled all of the community package, except for codetime, thinking, that, maybe, there is some conflict, but no, with all the other packages unloaded, it didn't affect the codetime memory usage.

[xavluiz]

Ok, thank you for the quick update. We'll take a look at this right away.
Regards.

[xavluiz]

We're still investigating this but I have a question in the meantime. Do you have a large number of files that you've worked on while using code time? We may be hitting a limit with how we help keep the hashed info locally. When you get a chance, can you provide the size of your "hashed_values.json" file located within your ~/.software directory? Thank you.

[igoryonya]

I have the same memory munching issue on recently installed, fresh computer at home and on a several years old installation at work.It takes 11GB of RAM on both computers. This file is from my home computer: [hashed_values.zip](https://github.com/swdotcom/swdc-atom/files/5615925/hashed_values.zip) I will send a file from my work computer, so you can compare them, tomorrow, after I come to work.

[xavluiz]

Ok, thank you for the file info. I'll confirm with another resource today and thank you again for your patience.

[xavluiz]

Would you be able to take a screenshot of the files within your .software directory with the file size info? Thanks.

[igoryonya]

This is from work:
hashed_values.json.zip

Here is the folder snap capture from work:

Will get the screenshot from my home computer after work.