MATLAB Service Crashes when disconnecting from MATLAB/quitting VS Code

[yismailsaadelgedawy]

Describe the bug
Upon trying to disconnect from MATLAB, either by by doing so manually in VS Code, or upon quitting VS Code via cmd+q or shutting down the PC, the MATLAB Service crashes and a MathWorks Crash Reporter window pops up, and the MATLAB instance persists for a while. If this occurs, it actually prevents my PC from shutting down!

To Reproduce
Steps to reproduce the behavior:

1. Open VS Code on a .m file
2. Wait until VS Code establishes a connection with MATLAB
3. cmd+q to quit VS Code (or disconnect from MATLAB manually)
4. You will see the crash window pop up

Expected behavior
For the MATLAB service/instance to be terminated gracefully/normally, just as if you had MATLAB opened natively and you press cmd+q or close the window via the red Close Button 🔴

Screenshots

(Fig. 1 - Activity monitor before connecting to MATLAB via VS Code)

(Fig. 2 - Activity monitor after connecting to MATLAB via VS Code)

(Fig. 3 - Activity monitor after disconnecting from MATLAB, showing instance persistence and MathWorks Crash Reporter)

(Fig. 4 - Elaborating on manual MATLAB disconnection without terminating VS Code itself)

Useful Information

• MATLAB Version: 25.1.0.2973910 (R2025a) Update 1
• OS Version: macOS, 15.6.1, 24G90
• VS Code Version: 1.109.3, arm64

[dklilley]

Hi @yismailsaadelgedawy , thanks for reaching out about this issue!

Can you confirm which version of the MATLAB extension for VS Code you are using? Did this issue only start recently?

[yismailsaadelgedawy]

Hi @yismailsaadelgedawy , thanks for reaching out about this issue!

Can you confirm which version of the MATLAB extension for VS Code you are using? Did this issue only start recently?

mathworks.language-matlab@1.3.8

I have been using this extension since September last year, and to be honest I don't think this used to happen.

[yismailsaadelgedawy]

Hi! Any updates on this @dklilley ?

[dklilley]

Thanks for the extra info @yismailsaadelgedawy! We will need to try to reproduce this on our end.

In the meantime, if you could share the crash log from MATLAB, that would be helpful! I believe you can copy it after expanding the "> Details" section of the crash dialog. Or, this page should help direct you to the location of the crash logs.

[yismailsaadelgedawy]

Here you go @dklilley

c7ec4576-0e95-4d95-aac7-81c48162b5a1.dmp

from:

Crash Report:
/Users/youssef.elgeddawy/Library/Application Support/MathWorks/wQ7pVWMabXDmrBh3YAbd0an9lL4hQ2wFzMvzXWmEDTM/crash_reports/completed

[baptisteikt]

I have had this issue for a few months and wrote to the technical support about it, here is their answer:

23.01.26
"I am writing in reference to your Technical Support Case 08374364 regarding 'Help troubleshooting recent MATLAB crash'.

This is a known issue starting with MATLAB R2025a. We currently

don't have a workaround unfortunately.

Please use MATLAB R2024b in the VS Code / Codium extension for the time being.

You will be notified automatically when the issue is fixed."

crash logs:

a9cabef0-7295-49c5-8d72-200fc57ef60e.dmp

[dklilley]

Hi @baptisteikt - thanks for sharing that additional info!

I was able to look this up internally and can confirm that this is a known issue which impacts R2025a and R2025b on Mac. As mentioned in the above quote, the best workaround at this time is to use R2024b.

Since this issue stems from MATLAB itself, and not the MATLAB extension for VS Code, I am going to mark this issue closed for now. If you would like to be automatically notified when this issue is resolved, I would suggest reaching out to MathWorks Technical Support and referencing case number 08374364.