New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
High CPU usage related to 3.12 in dashboard only #5354
Comments
Another case, is related to Ninja Forms. https://secure.helpscout.net/conversation/1988914598/363935?folderId=2683093 update: the proposed fix worked on this case |
This can be reproduced by installing WP Rocket 3.12.0.3 and Ninja Forms |
Another one, related to Ninja Forms: |
Problem seems to be related to those specific lines, commenting them out fixes it: wp-rocket/inc/Engine/Preload/Admin/Subscriber.php Lines 47 to 48 in c09453b
Solution proposed by @Tabrisrp is to change those lines to:
It fixes the problem, we need further investigation why it happens only on a very small minority of users. |
Related - https://secure.helpscout.net/conversation/1990404062/364232/ wp-rocket/inc/Engine/Preload/Admin/Subscriber.php Lines 47 to 48 in c09453b
|
Starting from those two lines: wp-rocket/inc/Engine/Preload/Admin/Subscriber.php Lines 46 to 49 in fd8afaf
So when we add the subscriber in the event manager class here:
and will pass the following values
Then it'll get into the following condition
and based on that, the values that will be passed to add_callback method are as follows:-
Notice that this priority has a string value and this should be number and this is the problem. the problem is on this line from WP core https://github.com/WordPress/WordPress/blob/master/wp-includes/class-wp-hook.php#L85 So the question is why with some plugins we see this problem like ninjaforms? I logged the this callback has more than 25500 lines and this is extremely big number
Also as @Mai-Saad mentioned, the issue is happening only with PHP >= 8 I'm going to create a PR for this now. |
Before submitting an issue please check that you’ve completed the following steps:
Describe the bug
It looks we have kind of loop in dashboard caused by incompatibility with 3rd parties. Notices are displayed in a loop until the timeout/fatal error happens.
To Reproduce
We still don't know how to reproduce it. For now suspected conflicts are:
Screenshots
Additional context
Add any other context about the problem here.
Backlog Grooming (for WP Media dev team use only)
The text was updated successfully, but these errors were encountered: