Maccy After being used in the background for many times, the memory occupation increases linearly

[iHzx]

Operating environment

• Device: MacBook Pro 14`2021
• macOS: Monterey 12.3
• Maccy Version: 0.22.2

Describe the problem

After running Maccy for a long time and using it for many times, the memory occupation of the application will gradually increase (it seems to grow linearly and there is no sign of release). It can be recovered after restarting the application.
I hope the author can fix this problem, thank you.

[pbond630]

Device: MacBook Pro 14`2021
macOS: Monterey 12.3.1
Maccy Version: 0.22.2

I have this same issue; when Maccy starts on my machine, it uses 24.9MB ram. After some time (several days), ram usage goes up to 350-500MB. Clearing the history doesn't reclaim any ram; closing and restarting Maccy does.

There's clearly a memory leak going on somewhere.

[cemetary]

Device: MacBook Air (M1)
macOS: Monterey 12.3.1.
Maccy Version: 0.22.2

In my case Maccy takes up 1.38 GB.

[p0deje]

The way Maccy uses Core Data could probably be improved to avoid memory bloat - right now every new copy is kept in-memory so if you copy large images (for example) - it can increase over time. I need to see if there is a way to make Core Data work in a different way by offloading unused items from memory.

[pbond630]

Alex thx for this.

From the behaviour I've seen on my machine, it appears that references even to deleted items are being retained. The memory usage remains the same even after deleting all items by doing a 'Clear'.
Shutting down & restarting Maccy is the only way to reclaim the memory.

[divaltor]

What's the status of this issue?

[p0deje]

No progress at the moment.

[Laicure]

Is it the same how Microsoft Windows store (Windows+V) clipboard items, via memory?

I'm thinking if there should be an option to store locally or via memory.

[chunyang-wen]

Maybe users have set a large history size? And a lot of images copied.(Just random guess)

[nicolaerario]

Maybe users have set a large history size? And a lot of images copied.(Just random guess)

It's not the case: I can reproduce with small text entries also. Just wait some time and the memory increase progressively

[avichou]

it often gets dangerously close to 2gb...

[p0deje]

I've been looking into this issue a few times already and I don't know what can be improved at the moment. Here is a simple video showing that Maccy keeps text/images in memory but offloads at least a portion of it whenever it's closed.

1. Start with clean Maccy. ~36MB
2. Copy long text. ~41MB
3. Copy screenshot. ~120MB when Maccy is visible, ~80MB when closed

If somebody understands Core Data and ways to lower memory consumption, I'd be happy to implement the recommendations, but I don't know what to do with this.

o.mp4

[tony-swg]

cring😭 1.2GB

[tony-swg]

cring😭 1.2GB

3.8GB now

[p0deje]

@tony-swg Do you copy lots of images or just text?

[tony-swg]

@tony-swg Do you copy lots of images or just text?

yes, both

[oraoraroa12313]

After updating my system to Sonoma and Maccy to latest version, with each opening (command shift c) the memory usage increases by around 300kb

[INikonI]

Same issue

[bombastiik]

4 GB...

[p0deje]

Folks, I get it - there is no need to post screenshots of RAM usage. It would be more helpful if someone would actually suggest ways to reduce the memory overhead or, ideally, send a PR.

[noahhhi]

Folks, I get it - there is no need to post screenshots of RAM usage. It would be more helpful if someone would actually suggest ways to reduce the memory overhead or, ideally, send a PR.

I have no idea what cause this problem. But I suggest you could publish a build with regular relaunch the main program for quick fix.

[coopfidgets]

Has this memory leak been fixed yet?

Maccy's memory leak is draining my RAM!

[soko1]

I suggest a temporary solution - restart the program every hour using crontab.

Open a terminal, enter the command crontab -e (if you are afraid that you will not be able to exit Vim :D, then use the command EDITOR=nano crontab -e), then enter the line:

* 1 * * * killall Maccy && /Applications/Maccy.app/Contents/MacOS/Maccy &

save changes.

It should look like this:

$ crontab -l
* 1 * * * killall Maccy && /Applications/Maccy.app/Contents/MacOS/Maccy &

[mishra-aayush-work]

For me the RAM usage was ~12 GBs, Quitting didn't help.

So I deleted everything and reinstalled it.

[Pil0tXia]

I appreciate this software and hope this issue can be resolved promptly. As this software has been developed and maintained by the author for a long term, very few people are familiar with this project besides the author. While waiting for contributions from the open source community may not be the most effective solution for a quick fix, I also hold hope that a kind soul might come forward to address this issue.

[Chen1Plus]

Is it tried to free some history from memory (and save it to disk) when the memory usage exceed a limit? If not, I think this can be a temporary solution.

And maybe it's possible to ask Microsoft that how win + v works when user copying lots of image.

[p0deje]

Folks, please share how things work for you on Maccy 2.0+

[MNeverOff]

Folks, please share how things work for you on Maccy 2.0+

I'd say it's definitely better, well done with the rewrite and thank you so much for all the efforts!
I'd still say that it's way over what I'd expect, and when restarting it falls down to ~50MB, so maybe not quite solved?

[Tyson1986]

Mine is the same

[kra-mo]

A little more robust workaround than #384 (comment) that avoids killing Maccy while currently open:

https://gist.github.com/kra-mo/e404d594d3d1c18e4db37013c9bec694

Just put it in ~/Library/LaunchAgents ^^