[erlang-bugs] Re: [erlang-questions] R13B stop_select error

[Thijs Terlouw]

Thanks for the detailed reply!

I have read the original bug reports in the mailing list, but I was not
totally sure if the bug you fixed was related to the problems I was seeing.
I indeed only started to experience these errors after I switched to R13B
(skipped R13A) and we are running Linux with SMP enabled. I've not had
problems with crashing VM and the problem has been quite hard to replicate.
I'm very happy you resolved this problem. Thanks again and look forward to
R13B01

Thijs Terlouw, Tencent

On Wed, Jun 3, 2009 at 5:23 PM, Sverker Eriksson
<sverker@REDACTED>wrote:

> Thijs Terlouw wrote:
>
>> Could you elaborate on the effects of this bug? I also have encountered
>> this
>> problem and was wondering if it can cause a problem I have encountered in
>> my
>> application (where the app seems to run fine, but seems not to be
>> processing
>> TCP requests anymore). Is there a public timetable for the release of
>> R13B01?
>>
>>
> The bug caused access of freed memory that used to contain general
> information about file descriptor events for the VM. We have seen different
> effects of this. I suggest you read the two cases posted in the original
> thread in erlang-questions:
>
>
> http://www.erlang.org/cgi-bin/ezmlm-cgi?4:sss:43685:200905:pcjfcbbfinlhdllhjhme#b
>
> In another case of a paying customer, the bug caused the VM to crash.
> Your case of "not processing TCP requests anymore", sounds like it very
> well could be caused by this bug. Especially if you get the error log from
> driver_select when that happens. The bug does only exist on R13,
> non-Windows, with SMP-support.
>
> R13B01 is scheduled to be released on June 10.
>
>
> /Sverker, Erlang/OTP, Ericsson
>
>
>


-- 
Thijs Terlouw,
Shenzhen, China
http://www.startinchina.com