Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Memory is growing up to 2-4GB after some time - how to debug? #3614

Open
muescha opened this issue Mar 7, 2024 · 8 comments
Open

Memory is growing up to 2-4GB after some time - how to debug? #3614

muescha opened this issue Mar 7, 2024 · 8 comments
Assignees

Comments

@muescha
Copy link
Contributor

muescha commented Mar 7, 2024

Is there any short way to see what is the cause of this increasing memory? When I (re)start Hammerspoon it is around 160MB - but growing up to 2-4GB

In some form to print out current memory usage of hammerspoon in the console?
or something else to see what is the reason?
can I somehow dump the used memory of hammerspoon to see which objects are still exisiting and not garbage collected?

@tedpearson
Copy link

Mine was just using like 40GB. And has been unresponsive a lot lately. :(

@ChillarAnand
Copy link

I am facing a similar issue. Memory usage is going up to 40GB and macOS is throwing that it is out of memory.

Screenshot 2024-06-17 at 10 55 30

I am doing frequent restarts as of now. Looking for a better solution.

@tedpearson
Copy link

I wonder if this is related to #3565. I've downgraded to 0.9.97 (6267) and am not having issues on this version.

@cmsj
Copy link
Member

cmsj commented Aug 5, 2024

It's interesting, I hadn't seen this issue previously, but I am starting to run into #3652 which could be related.

@cmsj cmsj self-assigned this Aug 5, 2024
@cmsj
Copy link
Member

cmsj commented Aug 5, 2024

There aren't a lot of places where we could be leaking RAM. One would be Lua itself, although all of those objects ought to be tiny, the other would be things like the hammerspoon console's scrollback. Beyond that it's possible we do have a leak bug somewhere which your configurations are hitting particularly badly. Unfortunately none of these are particularly easy to track down with some kind of runtime dump of objects, so we'll need to try and isolate what's triggering it, and dig into that.

If anyone is feeling adventurous, and ideally also experiencing this a lot, narrowing down your config to the smallest possible setup that triggers it, would be super helpful.

@cmsj
Copy link
Member

cmsj commented Aug 5, 2024

Hopefully this will be somewhat improved by the same merge that mitigates #3565

@latenitefilms
Copy link
Contributor

FWIW - I haven't had anyone report issues in CommandPost, so must be something specific in a config I think.

@muescha
Copy link
Contributor Author

muescha commented Aug 15, 2024

maybe related to this: at least there are debugging tips using activity monitor:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants