[erlang-questions] Patch package OTP 17.5.6.10 released

Rickard Green rickard@REDACTED
Thu Oct 11 21:57:47 CEST 2018


Patch Package:           OTP 17.5.6.10
Git Tag:                 OTP-17.5.6.10
Date:                    2018-10-11
Trouble Report Id:       OTP-13424, OTP-13866, OTP-13869, OTP-14159,
                          OTP-14514, OTP-14590
Seq num:                 ERL-340, ERL-474
System:                  OTP
Release:                 17
Application:             erts-6.4.1.7
Predecessor:             OTP 17.5.6.9

  Check out the git tag OTP-17.5.6.10, and build a full OTP system
  including documentation. Apply one or more applications from this
  build as patches to your installation using the 'otp_patch_apply'
  tool. For information on install requirements, see descriptions for
  each application version below.

  ---------------------------------------------------------------------
  --- erts-6.4.1.7 ----------------------------------------------------
  ---------------------------------------------------------------------

  The erts-6.4.1.7 application can be applied independently of other
  applications on a full OTP 17 installation.

  --- Fixed Bugs and Malfunctions ---

   OTP-13424    Application(s): erts
                Related Id(s): OTP-10336

                A process communicating with a port via one of the
                erlang:port_* BIFs could potentially end up in an
                inconsistent state if the port terminated during the
                communication. When this occurred the process could
                later block in a receive even though it had messages
                matching in its message queue.

                This bug was introduced in erts version 5.10 (OTP
                R16A).


   OTP-13866    Application(s): erts

                Calls to erl_drv_send_term() or erl_drv_output_term()
                from a non-scheduler thread while the corresponding
                port was invalid caused the emulator to enter an
                inconsistent state which eventually caused an emulator
                crash.


   OTP-13869    Application(s): erts

                Driver and NIF operations accessing processes or ports
                could cause an emulator crash when used from
                non-scheduler threads. Those operations are:

                -- erl_drv_send_term()

                -- driver_send_term()

                -- erl_drv_output_term()

                -- driver_output_term()

                -- enif_send()

                -- enif_port_command()


   OTP-14159    Application(s): erts
                Related Id(s): ERL-340

                Fix bug in binary_to_term for binaries created by
                term_to_binary with option compressed. The bug can
                cause badarg exception for a valid binary when Erlang
                VM is linked against a zlib library of version 1.2.9 or
                newer. Bug exists since OTP 17.0.


   OTP-14514    Application(s): erts

                Fixed bug in operator bxor causing erroneuos result
                when one operand is a big *negative* integer with the
                lowest N*W bits as zero and the other operand not
                larger than N*W bits. N is an integer of 1 or larger
                and W is 32 or 64 depending on word size.


   OTP-14590    Application(s): erts
                Related Id(s): ERL-474

                Fixed bug in binary_to_term and binary_to_atom that
                could cause VM crash. Typically happens when the last
                character of an UTF8 string is in the range 128 to 255,
                but truncated to only one byte. Bug exists in
                binary_to_term since ERTS version 5.10.2 (OTP_R16B01)
                and binary_to_atom since ERTS version 9.0 (OTP-20.0).


  Full runtime dependencies of erts-6.4.1.7: kernel-3.0, sasl-2.4,
  stdlib-2.0


  ---------------------------------------------------------------------
  ---------------------------------------------------------------------
  ---------------------------------------------------------------------




More information about the erlang-questions mailing list