[wp-trac] [WordPress Trac] #39338: class-wp-hook.php - apply_filters() infinite loop

[WordPress Trac]

#39338: class-wp-hook.php - apply_filters() infinite loop
--------------------------+-----------------------------
 Reporter:  frettled      |       Owner:  (none)
     Type:  defect (bug)  |      Status:  new
 Priority:  normal        |   Milestone:  Future Release
Component:  Plugins       |     Version:  4.7
 Severity:  critical      |  Resolution:
 Keywords:  has-patch     |     Focuses:
--------------------------+-----------------------------

Comment (by mordisko):

 This is still a problem.

 As a hosting provider we have hundreds of customers affected by this. The
 main problem is that an endless loop of errors generates thousands of
 gigabytes of error logs, which causes customers' quota to fill, which in
 turn ends up affecting more services than the WordPress itself.

 I understand the sentiment of trying to fully fix the underlying problem
 instead of applying a patch to prevent it from ever happening, but I do
 think that there has to be some middle ground here. How does having an
 endless loop help to find the issue? doesn't it make sense to stop the
 loop at some point, register or throw an error and move on?

 So far we have been unable to reproduce the error (and we devoted a lot of
 time to this) and the fact that this has been opened for quite a while now
 is forcing us to stop logging php errors altogether, which is a useful
 default feature for our end customers.

 We have been trying to diagnose this for a while now, but so far we
 haven't been able to find any patterns on plugins, themes or WP/php
 versions.

 It would be good to have a solution for this as it seems kind of strange
 to allow something like this to ever happen.

-- 
Ticket URL: <https://core.trac.wordpress.org/ticket/39338#comment:55>
WordPress Trac <https://core.trac.wordpress.org/>
WordPress publishing platform