I agree that it sounds very unlikely that they did not ever see this issue in testing, with one possible exception ... If what they are struggling with here is the very common (and often very difficult to resolve) problem of memory allocation and overwrite errors, then I can definately see that their testing may not have flushed this problem out. From what I have been hearing about the sometimes flakey behavior, my bet is that this is exactly what they are dealing with. Errors of this nature are very tough to find, and re-produce. In fact, they don't make applications behave in any consistant manner what so ever. You could run the same exact code the same way a thousand times in a row without a problem, and the next time that you run it the problem could occur. I don't know what their programming environment is here, but if it is C or C++ my money is that they are still dealing with a memory over-run error rather than some basic application logic error. It could be a simple as a single improperly sized malloc call, an un-terminated string, or a slew of other things. If this is the case, I can see how their testing hasn't flushed it out.