Conflict with Gravity Forms 2.5.3 about bugsnag-wordpress HOT 2 CLOSED

Hi @bhubbard.

Based on your second screenshot it looks like the problem is occurring due to there being more than 256 events in a single payload being sent to Bugsnag at once.

https://github.com/bugsnag/bugsnag-php/blob/2.10/src/Bugsnag/Notification.php#L140-L157 is the code in question. Each iteration removes an event so there must be more than 256 events in that payload to hit that limit. It would seem that whatever problem Gravity forms is encountering it is generating hundreds of warnings which is presumably what is causing the slowdown. Have you been able to determine the underlying cause of the error?

If you know that is an error/warning you can safely ignore you could also implementing the following
https://docs.bugsnag.com/platforms/php/wordpress/customizing-error-reports/#before-notify-callbacks
and preventing errors with that message from being sent to Bugsnag.

from bugsnag-wordpress.

Closing as we don't believe this is an issue with Bugsnag, it's just reporting the very high volume of warnings/errors being output.

from bugsnag-wordpress.