Plugin crashed my site temporary

I have several times been getting this wordpress error emailed to me from WP core. Not sure if others are experiencing the same errors. I also have Mailpoet 3 premium active.

Response from Query Monitor: This is a false positive in the fatal error handler in WordPress core, it states that Query Monitor causes the error but this is only because QM includes an error handler which causes it to appear in the error stack trace.

Looking at the stack trace, the problem actually comes from Mailpoet. The error suggests to me that your SQL server is under too much load and is crashing. You should speak with your host about this.

Response from Web host: Checking logs for the last week specifically for yesterday momentary downtime, there were 3 quick pings of activity but nothing going past 72% cpu and barely half of the available memory. I can’t speak to how much of anything mail poet is trying to use but I think it’s something specific to mailpoet or a plugin conflict with mailpoet considering it is always on the errors list. Especially considering there are plenty of resources left for it to utilize if it is running an intensive task.

Howdy! Since WordPress 5.2 there is a built-in feature that detects when a plugin or theme causes a fatal error on your site, and notifies you with this automated email. In this case, WordPress caught an error with one of your plugins, Query Monitor. First, visit your website (https://inpulsecpr.com/) and check for any visible issues. Next, visit the page where the error was caught (https://inpulsecpr.com/wp-login.php) and check for any visible issues. Please contact your host for assistance with investigating this issue further. If your site appears broken and you can’t access your dashboard normally, WordPress now has a special “recovery mode”. This lets you safely login to your dashboard and investigate further. To keep your site safe, this link will expire in 1 day. Don’t worry about that, though: a new link will be emailed to you if the error occurs again after it expires. When seeking help with this issue, you may be asked for some of the following information: WordPress version 5.4 Current theme: Consulta Child (version 1.0.0) Current plugin: Query Monitor (version 3.5.2) PHP version 7.3.16 Error Details ============= An error of type E_ERROR was caused in line 82 of the file /home/pdsinpcpr/public_html/wp-content/plugins/query-monitor/collectors/php_errors.php. Error message: Uncaught PDOException: SQLSTATE[HY000]: General error: 2006 MySQL server has gone away in /home/pdsinpcpr/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php:98 Stack trace: #0 /home/pdsinpcpr/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOConnection.php(98): PDO->query(‘SELECT t0.name …’) #1 /home/pdsinpcpr/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/dbal/lib/Doctrine/DBAL/Connection.php(736): MailPoetVendor\Doctrine\DBAL\Driver\PDOConnection->query(‘SELECT t0.name …’) #2 /home/pdsinpcpr/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/Persisters/Entity/BasicEntityPersister.php(699): MailPoetVendor\Doctrine\DBAL\Connection->executeQuery(‘SELECT t0.name …’, Array, Array) #3 /home/pdsinpcpr/public_html/wp-content/plugins/mailpoet/vendor-prefixed/doctrine/orm/lib/Doctrine/ORM/EntityRepository.php(167): MailPoetVendor\Doctrine\ORM\Persiste