Announcement

Collapse
No announcement yet.

PHP 7.3.1 Lands A Bunch Of Fixes For This Fastest PHP Release Yet

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • PHP 7.3.1 Lands A Bunch Of Fixes For This Fastest PHP Release Yet

    Phoronix: PHP 7.3.1 Lands A Bunch Of Fixes For This Fastest PHP Release Yet

    For those that wait for a point release or two before upgrading to a new PHP release on your development box or web server, PHP 7.3.1 is out today as the first bug-fix release since last month's big PHP 7.3 release...

    http://www.phoronix.com/scan.php?pag...7.3.1-Released

  • #2
    Originally posted by phoronix View Post
    Phoronix: PHP 7.3.1 Lands A Bunch Of Fixes For This Fastest PHP Release Yet

    For those that wait for a point release or two before upgrading to a new PHP release on your development box or web server, PHP 7.3.1 is out today as the first bug-fix release since last month's big PHP 7.3 release...

    http://www.phoronix.com/scan.php?pag...7.3.1-Released
    The link to PHP.net does not work.

    Comment


    • #3
      when you follow the bugtracker it's pretty clear that 7.3.x is far away from production ready
      just looking in the NEWS file what problems are prepared for 7.3.2 makes it clear
      crash bugs, memory corruption, wrong optimizer and code behavior....

      and for many of the issues after 7.3.0 was released i ask my self why do all the fuckrs out there up to big frameworks not test release candidates at all

      - Core:
      . Fixed bug #77369 (memcpy with negative length via crafted DNS response). (Stas)
      . Fixed bug #77387 (Recursion detection broken when printing GLOBALS).
      (Laruence)
      . Fixed bug #77376 ("undefined function" message no longer includes
      namespace). (Laruence)
      . Fixed bug #77357 (base64_encode / base64_decode doest not work on nested
      VM). (Nikita)
      . Fixed bug #77339 (__callStatic may get incorrect arguments). (Dmitry)
      . Fixed bug #77317 (__DIR__, __FILE__, realpath() reveal physical path for
      subst virtual drive). (Anatol)

      - Fileinfo:
      . Fixed bug #77346 (webm files incorrectly detected as
      application/octet-stream). (Anatol)

      - GD:
      . Fixed bug #73281 (imagescale(…, IMG_BILINEAR_FIXED) can cause black border).
      (cmb)
      . Fixed bug #77272 (imagescale() may return image resource on failure). (cmb)
      . Fixed bug #77391 (1bpp BMPs may fail to be loaded). (Romain Déoux, cmb)

      - Mbstring:
      . Fixed bug #77428 (mb_ereg_replace() doesn't replace a substitution
      variable). (Nikita)

      - MySQLnd:
      . Fixed bug #75684 (In mysqlnd_ext_plugin.h the plugin methods family has
      no external visibility). (Anatol)

      - Opcache:
      . Fixed bug #77266 (Assertion failed in dce_live_ranges). (Laruence)
      . Fixed bug #77257 (value of variable assigned in a switch() construct gets
      lost). (Nikita)
      . Fixed bug #77434 (php-fpm workers are segfaulting in zend_gc_addre).
      (Nikita)

      - PCRE:
      . Fixed bug #77338 (get_browser with empty string). (Nikita)

      - PDO:
      . Fixed bug #77273 (array_walk_recursive corrupts value types leading to PDO
      failure). (Nikita)

      - PDO MySQL:
      . Fixed bug #77289 (PDO MySQL segfaults with persistent connection).
      (Lauri Kenttä)

      - SOAP:
      . Fixed bug #77410 (Segmentation Fault when executing method with an empty
      parameter). (Nikita)

      - Sockets:
      . Fixed bug #76839 (socket_recvfrom may return an invalid 'from' address
      on MacOS). (Michael Meyer)

      - SPL:
      . Fixed bug #77298 (segfault occurs when add property to unserialized empty
      ArrayObject). (jhdxr)

      - Standard:
      . Fixed bug #77395 (segfault about array_multisort). (Laruence)
      . Fixed bug #77439 (parse_str segfaults when inserting item into existing
      array). (Nikita)
      Last edited by hreindl; 01-10-2019, 01:29 PM.

      Comment


      • #4
        Originally posted by hreindl View Post
        when you follow the bugtracker it's pretty clear that 7.3.x is far away from production ready
        just looking in the NEWS file what problems are prepared for 7.3.2 makes it clear
        crash bugs, memory corruption, wrong optimizer and code behavior....

        and for many of the issues after 7.3.0 was released i ask my self why do all the fuckrs out there up to big frameworks not test release candidates at all

        (list of bugs removed)
        Always keep in mind this: "Software without bugs is a pipe dream."

        Comment


        • #5
          Originally posted by NotMine999 View Post

          Always keep in mind this: "Software without bugs is a pipe dream."
          i am not dumb - but compared to 7.3 the upgrades to 7.1/7.2 where a no-brainer and it will be interesting if all the shiny benchmarks are repeated after 7.3 is *really* stable because a lot of fixes after 7.3.0 look like revert optimizations in compiler/opcache

          Comment


          • #6
            Hmm, where is uid313 ? He normally posts feedback on all PHP articles

            Comment


            • #7
              Originally posted by Vistaus View Post
              Hmm, where is uid313 ? He normally posts feedback on all PHP articles
              I am around!
              Not much exciting with minor bug fix releases. Maybe upcoming 7.4 will be more interesting.
              Either way, I haven't really touched PHP in a long time.
              Today I wrote JavaScript, and C#, yesterday was Python, last week was Java (on Android) .
              I don't do much PHP these days anymore.

              Comment

              Working...
              X