Cannot open variables from workspace in 2025a/b

I cannot seem to open variables in the variable viewer in 2025a or 2025b. The behavior is very inconsistent. For some variables, I can initially open them from the workspace by double clicking. A few minutes into my session, I will be unable to open the variables by double clicking. Sometimes when doing this, it will open a variable viewer window and not show anything (either it seems to be stuck on loading the actual content of the variable, or it appears to think it loaded the content without displaying anything). Other times, double clicking a variable does absolutely nothing. It does not work if I right click -> open selection either. When this happens, I CAN see the content of the variables if the variable is accessed through the command window, but this is not the most convenient method for exploring large structs, etc. I've tried reinstalling, regenerating my preferences folder, etc. These did not help. This is super frustrating and makes all 2025 versions largely useless for me.

[Stephen23]

What OS are you using?

File a bug report here: https://www.mathworks.com/support/contact_us.html

[Samantha Michalka]

Having the same issue on Mac OS - just updated to Tahoe. M1 chip.

[Adam]

I'm having a similar issue. A few minutes into a MATLAB session, I become unable to open a variable. For me, it's specifically a MATLAB table - arrays seem to work fine.

MacOS Tahoe 26.0.1, 2021 MacBook Pro M1 Max chip. MATLAB 2025b.

[Will Snyder]

Hi, I am having the same problem right now as well. Cannot open any tables to view the variable, but I can print the whole table to the command window area.

MacOS Tahoe, M1 Max chip, Matlab 2025b

[xingxingcui]

R2025a was a major update and currently has many bugs. R2025b is said to be a stability-focused release with no new features; I haven't tried it either. Do you recommend using R2026a or an earlier older version?

[半瓶君乐宝]

我也遇到了同样的问题

I encountered the same problem.

Answer 1

[Cris LaPierre]

Please report any product usage issues directly to MathWorks here.