MATLAB R2025a on Windows 11 [background open after closed]

Description:

I recently installed MATLAB R2025a on Windows 11, and I’ve noticed a serious issue with the way it terminates. After closing MATLAB, either by exiting the application or using the exit command, the related processes remain active in Task Manager and continue consuming the same amount of memory as when MATLAB was running. Each time I reopen MATLAB, new processes are created without the old ones being cleared, and after several open/close cycles, my system memory becomes completely filled, causing the computer to slow down or malfunction. I also observed that MATLAB 2025a uses significantly more RAM compared to previous releases, which I suspect may be related to the new desktop theme. Additionally, I connect MATLAB with VS Code, and the issue still occurs in this setup. Could you please help investigate and suggest a solution?

MATLAB Version: 25.1.0.2943329 (R2025a)

MATLAB License Number: ****

Operating System: Microsoft Windows 11 Pro Version 10.0 (Build 22621)

Java Version: Java is not enabled

[Matt J]

THat definitely sounds like something you should report.

[Janis]

having same problem with command line calls with -r and -batch. Same in 2025a and 2025b. I'm gonna report this. Matlab.exe processes are left open. Matlab window might close (-r). With -batch it doesn't finish (powershell stuck)).

I realized in my CI pipelines. Workaround ist to let matlab taskkill itself (exit and quit don't work properly) and read exit code from a previously written .txt .

Answer 1

[dpb]

While this <has been reported previously>, if you have ensured you have installed the latest release and the problem still exists, submit an official support request/bug at <Product Support Page>.

<The present workaround> is to be to manually close/terminate processes in Windows with the Task Manager.

Answer 2

[Steven Lord]

If the processes you're seeing remaining open are matlabwindowhelper processes, see Bug Report 3724070. Follow the bug report and you'll be notified when the bug is reported fixed.

[Steven Lord]

FYI this is reported fixed in release R2025b.