WordPress 4.9.3 Rescheduled for February 5th

WordPress 4.9.3 is a maintenance release and was originally scheduled to be available on January 30th. However, due to ongoing tickets and a short time frame to test the release candidate, it has been pushed back to February 5th.

WordPress 4.9.3 RC 1 is available for testing. This release removes JSHint from the code editors due to conflicts with the GPL License. If your code relies on JSHint from Core, developers encourage you to update it to use a copy of JSHint.

Other changes in 4.9.3 include, avoiding page scrolling when navigating the media modal, a handful of improvements to the customizer, and more. Please test WordPress 4.9.3 on a staging site and if you encounter any bugs, you can report them on the Alpha/Beta section of the support forums.


5 responses to “WordPress 4.9.3 Rescheduled for February 5th”

  1. Hi there,

    I have been getting a lot of memory dump files lately with 4.9.2 Googling the issue somehow brought me here. Is this perhaps a problem that is going to be fixed in the next update? or is it a hosting issue? I have never had this before since I started this site 4 years ago, and I have been with as many hosts in that time, now with Siteground GoGeek, 1 of the only 3 recommended on wordpress.org, so you would think they are WordPress specialists, which I think they are. They are also very generous with their resource allocations, WP Max memory limit something like 768MB, and 512MB in wp-config. Their new shared servers are monsters. Funny thing is the site is flying like there is no tomorrow, so I guess I’m just stumped as to how these files came to be, I like to keep it all neat and tidy, but they keep coming back, each one 20MB. I have not added any new plugins since I moved to SG a month ago.

    • I’m experiencing the same thing Sean. I’m also with Siteground (1.5 years) and for the first time in 11 years using WordPress I’m seeing core.xxxx files. They’re populating every few minutes. Mine are bigger than yours (starting at 150MB and quickly ramping up to 350MB until the server stops them from being created.

      I’m crossing my fingers it’s something that will stop happening in a new release. Until then, I’ve disabled as many things as I can, and delete the files throughout the day.

      • I’m going to try to sound like I know what I’m talking about.

        I actually contacted Siteground about this. It appears all servers do this, no matter what CMS you are using. I read Drupal forums talking about memory dumps. You, or rather a senior server admin can limit their size, or disable them completely. You would only enable them if their was a problem, much like enabling wp debug in your config.php file. However, these core dump files are huge and practically unreadable by a human, so I’m not sure what you are supposed to do with them. But seeing as my site is loading faster than ever and all features/plugins are working, I managed to convince SG to turn this off. Why it was on in the first place was not made very clear, which is why I did my own research, aka Goooogling. With this all said, I’m not entirely sure there is a bug in WP which is causing this.

      • Most likely, these are caused by some plugins you use. I doubt it was caused by WordPress itself. My suggestion is to check error logs on the server, to see if you have errors logged, and that would point to specific plugins. Probably, you are using one or more plugins that are not compatible with WordPress 4.9.x.

        If you update/replace/fix these plugins, you should monitor these core.xxxx files, my guess would be that they would disappear.

        • I thought about that, however, I have not added any new plugins to my site since I moved it to Siteground just over a month ago, I never saw these files at any of my other hosts, just a myriad of other problems, hence the move. Right now my site is loading faster than ever, and all my plugins are working.

          Only 2 things happened to my site recently; my move to SG, and WP update to 4.9.2

          What I think was happening was somewhat normal, something similar to what will happen if you enable WP debug in your config.php file. You only really do this if you have an actual problem, which I don’t, otherwise you will fill up storage space for no good reason.

          I have read about this occurrence all over, even on Drupal and Magento installations, so no, I don’t think it was a bug in WP.

          As it is right now, SG have set the dump value to zero, and my site is still flying like there is no tomorrow, and this is shared hosting :-)


Subscribe Via Email

Enter your email address to subscribe to this blog and receive notifications of new posts by email.

%d bloggers like this: