Hey @alex008,
We do want to solve the issue, but in some of these cases, we can’t solve them with just the logs alone. 1.5.0 introduced a lot of new features including the ability multi-thread process so it’s possible that could be the issue.
Based on the ticket you submitted our development team asked for access to your system to troubleshoot the issue more closely. It looks like you never responded.
I can understand if you can’t, share your system access. But until we can get on a system and replicate the issue and debug it readily, we won’t be able to solve the problem directly by making guesses at what the issue could be. With thousands of hosts multiple versions of PHP, WordPress, MySQL, MariaDB, MSSQL, Apache, many other web servers, and different operating systems coupled with cross configurations it’s not easy to always solve these issues.
We test our processes on dozens of major hosts and have not been able to reproduce this issue. With thousands of different hosts and configurations, some of these issues are not easily solved. Eventually, we’ll get someone who will share access and at that point, we’ll be able to narrow down the issue and help solve the issue for the broader community of WordPress users that may be experiencing it. Until we can isolate it the best-recommended approach is to do as you have recommended and roll back to 1.4.7.2
Thanks for your patience~
