From 36e90ad779bd17bcbeb8174616aabb01d7666bad Mon Sep 17 00:00:00 2001 From: Erlang/OTP Date: Thu, 14 Jun 2012 15:13:56 +0200 Subject: Update release notes --- erts/doc/src/notes.xml | 46 ++++++++++++++++++++++++++++++++++++++++++++++ 1 file changed, 46 insertions(+) diff --git a/erts/doc/src/notes.xml b/erts/doc/src/notes.xml index 1a79263928..c73c52a92f 100644 --- a/erts/doc/src/notes.xml +++ b/erts/doc/src/notes.xml @@ -30,6 +30,52 @@

This document describes the changes made to the ERTS application.

+
Erts 5.8.5.2 + +
Fixed Bugs and Malfunctions + + +

+ On Linux systems using heart (erl -heart) and a + HEAR_BEAT_TIMEOUT less than default, heart could fire + even though Erlang was running fine after approx 298 to + 497 days (depending on kernel config). This was due to + the behaviour of the times(2) system call. Usage of + times(2) is now replaced with clock_gettime(2) and the + CLOCK_MONOTONIC clock, resulting in a more stable + solution. The Erlang VM itself has used clock_gettime(2) + on linux since before R12B, so this only affects the + heart program.

+

+ Own Id: OTP-10111 Aux Id: seq12075

+
+
+
+ + +
Improvements and New Features + + +

+ The extra memory barriers introduced by bug-fix OTP-9281 + were unnecessarily used also on tables without the + write_concurrency option enabled. This could + unnecessarily degrade performance of ETS tables without + write_concurrency on some hardware (e.g. PowerPC) + while not effecting performance at all on other hardware + (e.g. x86/x86_64).

+

+ OTP-9281 (R14B03): ETS tables using the + write_concurrency option could potentially get + into an internally inconsistent state.

+

+ Own Id: OTP-10048 Aux Id: OTP-9281

+
+
+
+ +
+
Erts 5.8.5.1
Improvements and New Features -- cgit v1.2.3