Watchman: Watchman taking up more than 1 GB of RAM
I’m running only Safari, Spotify, and Final Cut Pro on my computer yet it’s extremely slow and laggy.
My laptop is a 2012 MacBook Pro with upgraded 8GB RAM.
Can somebody explain why watchman is taking up more than a GB of memory when I’m not even using it?
Hum4n01d
All 9 comments
Just restarted my computer and watchman is back again with nothing running besides Safari and Spotify
Hum4n01d
on 29 Mar 2018
Watchman remembers the directories that you asked it to watch. watchman watch-list will show you what it is watching. watchman watch-del-all will cancel all of those watches until you next use a tool that starts a watch up again.
wez
on 29 Mar 2018
Ok, but I haven’t used watchman directly ever.
On Mar 28, 2018, at 10:14 PM, Wez Furlong notifications@github.com wrote:
Watchman remembers the directories that you asked it to watch. watchman watch-list will show you what it is watching. watchman watch-del-all will cancel all of those watches until you next use a tool that starts a watch up again.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hum4n01d
on 29 Mar 2018
You most likely installed it to do something with React Native. React Native uses watchman to respond to changes in your project and hot reload them.
wez
on 29 Mar 2018
Yes, that’s why I installed it. I haven’t used React Native in months though.
On Mar 29, 2018, at 8:10 AM, Wez Furlong notifications@github.com wrote:
You most likely installed it to do something with React Native. React Native uses watchman to respond to changes in your project and hot reload them.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hum4n01d
on 30 Mar 2018
You seem somewhat confrontational about this, and I'm not sure what you want to hear. If you run the commands that I suggested above, you will reveal what it was watching and be able to stop it. There are configuration options available to limit the scope of what it is watching that we can explore if you wish to keep using it, and you are certainly free to uninstall the software.
wez
on 1 Apr 2018
Sorry about my tone, I was pretty frustrated when I discovered this. I will run that command as soon as I can.
On Apr 1, 2018, at 9:49 AM, Wez Furlong notifications@github.com wrote:
You seem somewhat confrontational about this, and I'm not sure what you want to hear. If you run the commands that I suggested above, you will reveal what it was watching and be able to stop it. There are configuration options available to limit the scope of what it is watching that we can explore if you wish to keep using it, and you are certainly free to uninstall the software.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.
Hum4n01d
on 1 Apr 2018
I'll close this out for now; when you have time to work through this, please re-open this issue and we can continue.
wez
on 4 Apr 2018
Sorry about the big delay. I ran the watch-list command to find this:
~ watchman watch-list
{
"version": "4.7.0",
"roots": [
"/Users/**redacted**"
]
}
That explains a lot of memory use. I ran the watch-del-all command and the RAM usage went away.
Thanks @wez!
Hum4n01d
on 22 May 2018
Related issues
marco-ms
·
3Comments
rongliangduan
·
3Comments
the-simian
·
5Comments
williamcotton
·
6Comments
export-mike
·
4Comments
Most helpful comment
You seem somewhat confrontational about this, and I'm not sure what you want to hear. If you run the commands that I suggested above, you will reveal what it was watching and be able to stop it. There are configuration options available to limit the scope of what it is watching that we can explore if you wish to keep using it, and you are certainly free to uninstall the software.