livescript get stuck randomly

Hi,

I'm running a livescript for my analysis so I'm juggling back and forth to produce plot and other but from time to time, often after a bug, the script refuses to run neither section nor the full script.

The troubleshoot I've found is to close the livescript and open it again. It continues working even if I don't clean the variables after reopening it.

It's not an awfull problem but it is rather annoying so I was wondering if anyone else had this issue.

[Cris LaPierre]

Does this happen consistently or was it a one-time error?

[Tancredi Bernasconi]

It is not a one-time error. It happens roughtly 3-4 times during a full day work.

It seem to always happen after a bug in the code and I try to plot an array with the wrong indices or out of bound. But I can't figure out exactly a pattern when it happens and I cannot produce the "hang" consistently.

[Cris LaPierre]

What do you see when it hangs? Is there a spinning graphic by the first line? When it hangs, what happens if you click in the Command Window and press ctrl+C?

[Tancredi Bernasconi]

Well, matlab doesn't hang per se.

It's more that the livescript refuses to run. Whether I press the run button or for individual section. It just doesn't do anything as if I had not asked to run.

Otherwise the script remains editable and I can run things in the matlab window normally.

[Cris LaPierre]

That's actually what I would expect. Everything appears to be working but the live script doesn't execute. Try a ctrl+C the next time it gets like that and see if, after doing that, the live script code executes.

[Tancredi Bernasconi]

Hi,

I tried crtl+C but that doesn't seem to have any effect. (Except copying text)

[Cris LaPierre]

When the command window is active, ctrl+C kills whate ever is running in the background. It does not stop execution of live scripts, but sometimes a background process can be runnign that is preventing the script from running.

Did you click in the command window first before using ctrl+C?

If so, this may be another issue. I would suggest contacing support, especially if you can identify a consitant set of steps that reproduce the issue.