[erlang-questions] : Subtle behaviour of Erlang scheduler

[Sean Hinde]

On 29 May 2007, at 09:22, KatolaZ wrote:

>
> After we discovered a big bug in the scheduler, and reported it to the
> community, the only answer we got was: we don't use that scheduler
> code in OTP, this bug does not heavily affect OTP, processes in
> telecom apps usually use normal priority and since telecom apps are
> our main business and represent 90% of actual Erlang code, it does not
> matter for us.

I have been following this thread with interest, and I remember it  
quite differently to your description. What I saw was one mail from  
Rickard Green saying that the issue would be fixed in a future  
release, and a number of other people offering workarounds until that  
time, along with their experiences. I was rather heartened by this.

>
> Well, maybe it does not matter for telecom apps, maybe it does not
> matter for 90% of Erlang code, maybe it is a so rarely used feature,
> but ERLANG HAS A BUGGY SCHEDULER, EVEN IF YOU DON'T WANT TO ADMIT IT.

See above.

>
> The discussion is closed, also for me. But I would rather prefer to
> avoid this kind of mails......

Well, don't write them :-)

Sean