[erlang-questions] : Subtle behaviour of Erlang scheduler

Ulf Wiger (TN/EAB) ulf.wiger@REDACTED
Tue May 29 12:32:27 CEST 2007

Argh! The combination of using Outlook and having
emacs keyboard shortcuts wired into the brain is
also lethal...

I meant to write that running the original test
program with my patch still locks up, since 
'proc2' effectively keeps the shell process and
proc3 from ever executing. Proc1 dies as it should, 
since timer isn't loaded, but since the processes 
aren't linked, the others don't notice, and proc2 
keeps locking up the system, waiting for a message 
that will never arrive.

Changing the spawns to spawn_link will cause the 
program to terminate.

So we moved from one subtle problem to another one,
all having to do with the looping high priority

Obviously, if you have constant work on high priority,
the concrete effect will be that you starve all other
work, and there will be no useful prioritization 
anyway (all work getting done is done with the 
same priority.)

Ulf W

> -----Original Message-----
> From: Ulf Wiger (TN/EAB) 
> Sent: den 29 maj 2007 12:24
> To: Ulf Wiger (TN/EAB); me@REDACTED
> Cc: Erlang/OTP discussions
> Subject: RE: [erlang-questions] : Subtle behaviour of Erlang scheduler
> Just so the rest of you won't need to spend time pointing out 
> the obvious, the problem wasn't the high-priority process 
> calling timer, but the other high-priority process caught in 
> a busy loop.

More information about the erlang-questions mailing list