[erlang-bugs] 100% CPU usage on Mac OS X Leopard after peer closes socket

[Matthias Radestock]

Bjorn,

Bjorn Gustavsson wrote:
> Matthias Radestock <matthias@REDACTED> writes:
> 
>> On Mac OS X Leopard this results in {error,einval} being returned
>> (which is expected) and the beam process subsequently consuming 100%
>> CPU (though the Erlang shell remains responsive).
> 
> A simple patch that eliminates problem follows.

I can confirm that this does indeed fix the problem on our test system.

Thanks for looking into this and producing a patch so quickly.


Matthias.