Jump to content

Prevent `plasticd` from launching on startup


kjy5
 Share

Recommended Posts

I occasionally use Plastic SCM Cloud Edition to do version control and I noticed that the process plasticd will automatically get launched on startup. How can I prevent it from always starting up with my computer (taking up CPU and RAM time)? It is launched by launchd and is a root process. I am using macOS Monterey.

Thanks!

Link to comment
Share on other sites

Hi,

This is the local server service that is ran so you can host local repos in your machine. It's transparently installed and started so you can create local repos without worrying about intsalling a local server.

The process should be pretty light. Is it taking too much CPU and RAM?

Regards,

Carlos.

Link to comment
Share on other sites

It's using around 100 MB of RAM and about 0.2% of my CPU while my computer is idling. While this is small, it's kind of annoying given that I don't ever use local servers (I use Plastic Cloud) and not often enough. It would be great if there is some way for me to manually start up this process only when I need it.

Thanks!

Link to comment
Share on other sites

Thanks for the command! While this only helped to stop the service for the current login session, the path to the LaunchDaemon did help me utilize the following commands to remove it permanently [source]

sudo rm -rf /Library/LaunchDaemons/com.codicesoftware.plasticscm.server
sudo launchctl remove "com.codicesoftware.plasticscm.server"

I'm leaving this here for anyone else interested in disabling the local server.

Link to comment
Share on other sites

  • 1 month later...
On 11/26/2021 at 10:12 AM, calbzam said:

Hi,

This is the local server service that is ran so you can host local repos in your machine. It's transparently installed and started so you can create local repos without worrying about intsalling a local server.

The process should be pretty light. Is it taking too much CPU and RAM?

Regards,

Carlos.

I just followed kjy5's steps to uninstall the daemon as it was taking up 9GB (!) of system memory. Seems to have worked.

First time (when it was using 9GB of memory) I simply quit through Activity Monitor. Not long after my Mac complained about having run out of system memory, and sure enough, plasticd was using 7GB of memory. I kept Activity Monitor open and after a minute or so plasticd popped up again at around 1.4GB and climbing. Decided to uninstall then.

I'm on OS X 12.0.1.

Thought I'd let you know in this thread as you asked about plasticd taking up too much CPU / RAM.

  • Thanks 1
Link to comment
Share on other sites

Hi @wfk

Are you easily reproducing the issue if start the local Plastic server in macOS and leave it running for a few hours? I guess the load of your local server is low.

We would like to check the server logs when this issue happens.

Regards,

Carlos.

 

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...