diff options
author | Maxim Fedorov <[email protected]> | 2019-03-04 14:19:05 -0800 |
---|---|---|
committer | Lukas Larsson <[email protected]> | 2019-03-21 10:23:47 +0100 |
commit | 8368589a9b69b0c8f9d0e9a9c94f51f7afecafa8 (patch) | |
tree | 3fa4e86813c8f753fe67a58034126f6e14934852 /lib/kernel/test/appinc2B.erl | |
parent | 8ab1bc2af5933b36c1583b1168e9b7875334cd50 (diff) | |
download | otp-8368589a9b69b0c8f9d0e9a9c94f51f7afecafa8.tar.gz otp-8368589a9b69b0c8f9d0e9a9c94f51f7afecafa8.tar.bz2 otp-8368589a9b69b0c8f9d0e9a9c94f51f7afecafa8.zip |
erts: release dirty runqueue lock before entering endless loop when BEAM is shutting down
This patch fixes a problem happening when BEAM is shutting down. It is possible for a dirty scheduler to take the lock, and keep it, when the system is shutting down. It may also happen that a normal scheduler decides to schedule some dirty job (example is major garbage collection that results in migrating the process into dirty CPU queue), and hangs trying to take the lock that will never be released.
To fix the problem, either release the lock before entering endless wait loop, or reverse the order in which schedulers are stopped. Either fix works, and, of course, it works even better to apply both.
Diffstat (limited to 'lib/kernel/test/appinc2B.erl')
0 files changed, 0 insertions, 0 deletions