Why does Matlab get stuck in busy state before showing an error message or ending a script?

I can start Matlab and run programms without any time issues. When an error occurs it takes Matlab about two minutes to show the error message in the command window. During that time it is not responding and 'busy'. Same happens when a programm finishes it takes Maltab the same time to show the >> again. I tried different Versions from 2013a to 2014a. Everytime the same problem.

[per isakson]

Strange! Are files on a server involved? What happens if you do Cntrl-C during those two minutes?

[dpb]

Strange, indeed? Any chance still have an earlier release installed? Does it happen there, too, if so?

Is this a newly-developed symptom or is/has it been like this from initial installation?

[Flo]

Hi, it happens on 2013a and 2014a. CTRL+C doesnt work. It really freezes. Figures, command window, everything. All files are on local hard drive. That issue came up a few days i guess. I though it its the code after the last command of the whole file it just gets stuck. Is there something to reset Matlab settings, paths or anything?

[Flo]

OK it seems that it has to do with the actual code.. another programm works fine. In that faulty case i use many classes and handles.. might that be the reason?

[dpb]

Looks like a case of isolation by bisection or the like...can you piecemeal smaller sections of the overall script/function/app and thereby perhaps discover the point at which the problem arises?

Otherwise and w/o any code specifically, not sure there's much anyone can do here. If it's not terribly large and you can also provide data to make it standalone (and IP or other issues aside, of course), you can always try to post/attach the code/data and see if others can reproduce the problem.

It would be best by far, of course, to make a serious effort to minimize the size required to do so, first. And, doing that might just find the cure as a side benefit... :)

[per isakson]

Shots in the dark:

• Try to run without the "accelerator". At least it is an easy test: feature('accel','off')
• "many classes and handles" . Help Matlab with the cleaning up by some explicit delete(obj). Tricky dependencies?
• "after the last command" set a break point close to the end and step through the end of the code. Sometimes Matlab behaves differently in debug mode.

[Flo]

Ok, i tried those. It seems that deleting the object take 132 seconds. Creating it takes 20 seconds. Unfortunatelly it is essential that handles point circular. But still, how does it take so long to delete that object?

[Walter Roberson]

Which "object" is that which it is deleting?

[Flo]

OK lets say we got object "main". That includes map with values of type handle. There is map "a" and "b". An object from map "b" can reffer to an object in map "a" and vice versa. I now try to figure out if there is any speed up if i delete that link before deleteing so it does not get stuck in a circle.

[Walter Roberson]

Plausible. It's worth a try.

[Flo]

Ok Update. I tried to implicit delete every handle and object and Matlab tries to delete all connected handles as well. Not only once. Seems as it results in a big mess of deleting everything a few times.