Jonny

I have an intermittent crash happening on a huge involved patch with several mxj objects doing all sorts of stuff (and deadline racing towards me - hence the plea for help)

A typical crash-log is attached - the key bit i think, is the say_deferred call which then calls error, so i suspect it's where my Java calls error() to "post" an error to the Max window.

I have tried to split out smaller parts of the thing and test to destruction but without joy. Initially i suspected it might be the size of the message but i can post() and error() messages up to about 12MB (then the Java heap gets full and i get a polite exception message). It handles null strings happily and seems ok with foreign chars (much of this project is in Norwegian).

So, just posting here on the off chance someone might know something about this say_deferred, error, object_error, vsnprintf_zero route inside Max5?

P.S. I'm pretty sure this didn't ever happen in Max 4.6, but now it would be almost impossible to go back and check.

Max5 mxj crash (possible to do with say_deferred() / error()?)