MathWorksServiceHost issues (really slows down startup and then doesn't stop when matlab stops) in 2024a

With 2024a on Linux, when the matlab process starts, MathWorksServiceHost and MathWorksServiceHost-Monitor are started from the user's home directory, which REALLY slows down the startup when the home directory is mounted over the network. I've been able to mitigate the slowdown a bit by having $HOME/.MathWorks/ServiceHost get created a simlink to the local /tmp dir However...

MathWorksServiceHost and MathWorksServiceHost-Monitor don't stop when the matlab process stops. This is a problem on a multi-user system where, we then have a bunch of processes just hanging around for no reason.

This first issue is a problem, but not too major an issue, but the second would seem to me to be a bug.

Answer 1

[Chaitanya]

Hello Mike

I understand that you are facing issues with ‘MathWorksServiceHost’ where it slows down the MATLAB startup and you see that the ‘MathWorksServiceHost - Monitor’ don’t stop when the MATLAB process stops which leaves few processes not terminated.

It is recommended to uninstall and reinstall ‘MathWorksServiceHost’ when such issues are faced.

Please follow the steps mentioned in the following MATLAB Answer to do the same.

https://in.mathworks.com/support/search.html/answers/1815365-how-do-i-uninstall-and-reinstall-mathworks-service-host.html

I hope that the above information is helpful.

Thanks,

Chaitanya

[Mike VanHorn]

I appreciate your response after so long a time.

Is there anyway to just disable the service? We will never use MATLAB Drive, and if that is what MathWorksServiceHost implements, then it is useless to us, anyway.

[Randall]

@Mike VanHorn Thanks for posting this issue, we are facing the same thing on a new linux compute cluster. Did reinstalling MathWorksServiceHost help in any way?

[Mike VanHorn]

No, because it doesn't address the problem. The "problems" we've identified in this thread are by design, so re-installing would be the solution to the software not working in this way (which is the way we don't want them to work).

Answer 2

[Michael Greenburg]

I just wrote contain to combat this very problem--it can prevent those daemons from persisting after Matlab exits. We now put this script (but NOT the original matlab) in PATH:

#!/bin/bash

# Symlink their bloat directory to /tmp
if [[ -d ~/.MathWorks && ! -h ~/.MathWorks ]]; then
    mv ~/.MathWorks ~/.MathWorksOld
    echo "WARNING: moved ~/.MathWorks to ~/.MathWorksOld; unless you need it, remove ~/.MathWorksOld."
fi
test -h ~/.MathWorks || ln -s /tmp ~/.MathWorks

# Launch matlab, contained so the daemons can't escape
module load apptainer contain &>/dev/null
contain /apps/matlab/r2024a/bin/matlab "$@"

[Mike VanHorn]

Michael Greenburg,

That's a pretty cool script. I may use that for Cadence Virtuoso, too, as it has started doing to the same thing as Matlab in regards to superfluous daemons.