On Fri, 24 Mar 2006, Kris Jurka wrote:
> On Fri, 24 Mar 2006, David Blasby wrote:
>
>> [OutOfMemory errors leave protocol stream in unknown state]
>
> Yeah, that's a problem alright. The easiest thing to do is to treat an out
> of memory error like an IOException and destroy the whole connection
> immediately. This isn't terribly friendly though and the vast majority of
> the errors are going to come from ReceiveTupleV3, so we could put some checks
> in that path that could get the protocol back into a known state. Adding
> checks around every allocation isn't going to be worth the effort.
>
I've applied a patch for this to 8.0, 8.1, and HEAD cvs branches and new
official releases should hopefully be out soon.
Kris Jurka
