Omit trace results in Stack underflow?

Anyone come across this before?

If I turn ‘Omit trace actions’ on, then when I run the file, I get the error that says:
Stack underflow occurred.

Fortunately, it told me what class it occurred in, so I took out the traces one by one, and I found one particular line that causes the error. It’s just tracing a string, and it causes the error anywhere inside of this one function.

So I can easily avoid the error, by either erasing that one trace, or by turning ‘omit trace actions’ back off. But I don’t really get why it’s happening.

All that I can say, that this error message isn’t for developers, it’s for testing VM performance/errors. So, this is either a bug of VM, or some misspeling in your code… Basicaly, it means that you tried to make some action not even specifying the object you want to be affected. Something like ;+1; (it needs first operand to be a valid expression). But, if you say it’s a string in trace(), than, it’s probably a bug…