Have you upgraded to 7.3? Any trouble with bugs or stability issues?
Posted Jan 8, 2019, 10:16 PM UTC
2721
What I've looked at so far is the list of most recent bugs for 7.3 on bugs.php.net, including closed bugs.
Ondrej has patched two bugs since 7.3.0 was released: Infinite loop in preg_replace_callback and OPcache optimization problem for ArrayAccess->offsetGet(string).
5
The opcache bug caused serious issues for a personal side project. I ended up reverting back to 7.2 and will wait until 7.3.1 to try again.
3
indeed, the opcache bug was so random as well, like when i check the stacktrace i wonder how the fuck this random code managed to slip and when i go check the code it does not exists!! the transform to literal wasn't something i was expecting from opcache
1
Been using it in test / dev on code which is running live under 7.2. No problems so far ...
3
Been rock solid for me, but the application I maintain isn’t terribly complex.
3
Same here, just had to fix some warnings and install pecl-zip (not included anymore) . Using Smarty and good old libraries and no problems at all with production customers (on a critical day by day app use btw, but nothing extremely fancy)
1
I've been running it on my dev box since one of the late RC releases in preparation for an upgrade of a work project. The work project ended up getting bumped to 7.2 instead of 7.3 mostly for reasons of package availability in prod, but 7.3 has been just fine so far. I do worry about XDebug a bit, though I think one of the recent releases now claims support for 7.3.
2
I haven't been able to get xdebug to run with my rat trap configs in conjunction with PHPUnit that "worked" with 7.1.
Admittedly, that may have some to do with my rat trap configs.
No errors or particular problems-- except that I cannot step through my code. Just never talks with PHPStorm when I run my tests and I have the xdebug extension loaded-- and it is, I checked it with php -i. I even tried running php with the fpm config via cli, no dice. (xdebug works great with fpm & the fpm ini file.)
Meh.
2
XenForo 2 is badly broken on PHP probably due to opcache. I've actually had those issues firsthand before I read about them. Developers recommend rolling back to PHP 7.2.
More info: https://xenforo.com/community/threads/xenforo-2-0-12-released.157685/ and https://xenforo.com/community/threads/php-7-3-0-issues.157481/
1
opcache on crashes PHP almost every time. had to disable it. Everything else seems to work fine.
1
Did it on two Wordpress sites, no issues so far.
1
My conclusion is it's best to wait for 7.3.1 (that should be any day now) or even 7.3.2 due to Xdebug and multiple Opcache issues. Of course in the meantime one should continue testing locally and report bugs to bugs.php.net.
1
The Symfony server does not seem to run properly under 7.3.0 on ubuntu. It acts as though no server is available even though the process is running. I have to use:
php7.2 bin/console server:start
to get the server to run properly.
1
All good so far. The only problem I have is with phpMyAdmin. It works as intended but every time you try to do something there is a little warning about something. Really annoying
1
7.3.1 with xdebug working (on windows) which wasn't the case on 7.3.0.
However, now I can't get nginx to work, so something cahnged in this release too :-(
1
I attempted to upgrade the prod site I managed to 7.3.0 right when it came out, but PHP-FPM segfaulted about 20% of the time, stickily (like 5 requests in a row would segfault, then the next 10 would work, repeat +-3).
I hadn't seen segfaults like that since the dreaded 5.1.0 release! Disabling opcache seemed to fix it, but I figured if it was so unstable that I'd wait until bugs stopped popping up, but they haven't even been fixed yet.
I was then laid off about a week later on Christmas week and am currently looking for a remote PHP job. I'm willing to travel -anywhere- in the world to get started, and I have an American passport. Anyone who finds me such a job, I'll pay $1,000/month for the first year that I have the job.
1
What version are you upgrading from? I had multiple issues with 7.2 since the count() function now outputs warnings.
-1
It is not an issue, they added this warning in 7.2 for purpose
1
Don't know why you felt the need to reply to a 2 month old comment, but anyway... it is an issue because several frameworks turn warnings into fatal errors.
1
Hey there, I have answered because I was looking for informations about the PHP 7.3 stability :)
So the framework are not compatible with this PHP version. The PHP team did the change for the purpose. And all code which shows warnings needs to be fixed in order to work with this version :)
Cheers
1
The frameworks are perfectly compatible with the PHP version. Warnings or notices are escalated on older PHP versions too.
The problem is, warning are just that, warnings. In plain PHP you can upgrade and look at your logs for warnings then fix them. (Obviously you’d do your own testing first but you may not catch everything.)
But you can’t do that with certain frameworks (eg Laravel). It’s not a failing in the framework - in general it’s good that they halt on warnings because they could cause bigger issues. Anyway my original comment was just to give a heads up.
1
[removed]
-18
Problems with Xdebug compatibility. They might be resolved with the next Xdebug release.
This is the main thing holding me back at the moment.
Xdebug 2.7.0 will support php 7.3 Its currently at beta1
Tried it yesterday via pecl all was fine for a while but my local nginx started throwing 502 errors that i couldnt debug when the extension was enabled
Yeah. 2.7.0 is very crashy with 7.3 at the moment.