Matlab stops taking inputs...

Sometimes when I run a bad .m file Matlab will sort of become unresponsive... it's not a total lock up, because I can still type whatever I'd like in the workspace but after hitting return it just bumps me down a line and doesn't actually execute the command. Why is this and how do I avoid it / stop it?

[Matt J]

What do you mean by a bad .m file? What's bad about it?

Answer 1

[Matt J]

Sounds like MATLAB simply hasn't finished executing the previous commands. Be patient, or investigate why your previous commands are doing a bigger computation than you intended.

[Sean de Wolski]

Sounds right to me. Does it say busy in the bottom left corner?