I'm amazed that nobody on the BRL test team spotted this. All you have to do is leave a program running overnight and see what happens - standard practice in the games industry.
For starters, how about a managable bit of sourcecode that reproduces the issue? How about a little more detail about the bug?
Eikon has posted code in another thread which reproduces the error. That thread is now in the bugbin, amid claims from Mark that he's fixed it (when in reality it seems cause remains but the effect has changed). I guess he didn't think that actually testing it out was a wise use of his time and resources, either. Beyond that I have NO time to prove that MAX is not ready for public consumption -- all I know is it has a lot of problems and until sorted it is not usable.
Perhaps a little harsh, but as bugs go, this one is just about as bad as they get.