visdiff() is crashing continuously in R2025b

Dear all
i am experiencing a lot of crashes using visdiff() in R2025b, are experiencing them too?
Thanks in advance.
D

 Accepted Answer

Image Analyst
Image Analyst on 8 Mar 2026 at 15:01
Edited: Image Analyst on 8 Mar 2026 at 15:02
No. But I haven't used it. You are a man of very few words (perhaps because you never read the tutorial link below). I'm not sure how anyone could answer your question without all the missing information you forgot to include. For example
  1. Is it just the visdiff function that is throwing an error in red text in the command window?
  2. Is it the entire MATLAB environment that causes a crash and says something like MATLAB has encountered and error and needs to close.
  3. If #2, does it immediately, or after restarting MATLAB, create a crash dump file and ask you to send it in to tech support?
  4. Or do you get no crash dump and no dialog box asking you to send in the crash dump?
  5. What operating system are you using? Windows 11, iOS (what version), some flavor of unix?
  6. If it repeatable or is it intermittent?
  7. Will it always crash with the same two files, or does sometimes it work with those same two files?
  8. Does it occur with other files? All other files, or just files of a certain format?
  9. Does it ever work with any type of files, like flat text files (like .m files)?
  10. Are your files binary or have any non-ASCII characters in them?
  11. Do you want any of us to try it with your files?
  12. Do you have a maintenance agreement where you can call tech support and have them help you?
If you have any more questions, then attach your two files and code to read it in and pass it to visdiff with the paperclip icon after you read this:

5 Comments

Davide
Davide on 8 Mar 2026 at 16:26
Edited: Stephen23 on 8 Mar 2026 at 19:33
Hi,
thanks for the answer, and sorry, you are right, I try to answer to your questions:
1) matlab runs over window 11.
2) basically i use this command:
>> visdiff('init_model.m', 'D:\git\github\modelization-and-control\power_electronics_design_with_simscape\afe_inv_psm\init_model.m')
I have different projects all of them have an init file "init_model.m" and often i merge with the "master" source located at the second argoment of the visdiff() command.
3) it works fine but with a rate of one over five/seven it crashes in two/three different way:
A) it is not able to open the files, and wait and wait with a gray visdiff() window and after 30s it crashes saying nothing, absolutely nothing, matlab just dissapears. I have to run again matlab and in general it take two/three time to work properly.
B) it is able to open both files, i do my merging and when I save modification it does but also crashes as point A).
C) it is able to open both files but when I flip the comparison it crashes as above.
4) file of the first argument of visdiff() is often different, but the file of the second argoment is always the same.
5) I never used visdiff() with other files and file types.
6) this issue occur sometimes with a rate of one over fice/seven.
7) I am using a *.m file but is not a pure m file because I use them as live script. Is saved as m but I think is live script: maybe this could be the root causes...
8) I attached both files:
A) the user contains
[model, options] = init_environment('single_phase_cllc');
B) the master contains
[model, options] = init_environment('afe_inv_psm');
9) I don't need support and I don't know if I have some agreements, we pay maintenance every year, my license is XXXX. Anyway I just placed this question to understand if there were something already known... for me is not an issue, I overcome this small problem, and probably I think comes from misuse of *.m file... maybe.
Many thanks
D
Stephen23
Stephen23 on 8 Mar 2026 at 19:34
Edited: Stephen23 on 8 Mar 2026 at 19:34
"it is not able to open the files, and wait and wait with a gray visdiff() window and after 30s it crashes saying nothing, absolutely nothing, matlab just dissapears"
Ouch, that is pretty major, you should definitely contact TMW support about that!
"we pay maintenance every year"
Support is exactly why you pay maintenance: https://www.mathworks.com/support/contact_us.html
I wonder if it has some problem with github. If the github file is somehow synced up with the cloud then perhaps github has a locked, though I'd think you'd get some error like "cloud file provider not running" like I do sometimes with OneDrive files. Can you copy that file to a folder in a shorter, much simpler, non-github linked local folder (like "D"\test") and try it 10 or 20 times and see if it always works if github is not involved? I'll download your files and see if I get the same problem.
I wonder if it has something to do with github? Is the file somehow auotmatically synced with github, which might have it locked somehow? Though I'd think you'd get an error like "cloud file provider not running" error, though perhaps MATLAB crashes before it can give you any sort of error. I did download your files to some simple, non-git hub folders with simple names and ran your vsdiff command about 30 times and it never crashed on my Windows 11 system. If it works if you're not using anything to do with github, then maybe that's the problem.
Please see this article:
and send in the crash dump file it makes to tech support. You might as well get some support for what you pay. They can set up a screen sharing session and drive your computer to see what's happening.
Hi,
many thanks, yes git is a good point. Thanks for the link.

Sign in to comment.

More Answers (0)

Categories

Products

Release

R2025b

Tags

Asked:

on 8 Mar 2026 at 7:02

Commented:

on 9 Mar 2026 at 5:07

Community Treasure Hunt

Find the treasures in MATLAB Central and discover how the community can help you!

Start Hunting!