Azuracast: PHP Fatal error found later last update

[FiloSpaTeam]

Using Docker installation method
Yes

AzuraCast version
Rolling Release #bc307d2 (2020-10-21 12:52)

Host Operating System
Ubuntu 20.04

Describe the bug

PHP Fatal error:  Allowed memory size of 268435456 bytes exhausted (tried to allocate 520192 bytes) in /var/azuracast/www/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php on line 141

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 520192 bytes) in /var/azuracast/www/vendor/doctrine/dbal/lib/Doctrine/DBAL/Driver/PDOStatement.php on line 141

To Reproduce
Spawn inside logs

Expected behavior

Relevant Logs

Screenshots

Device(s):

Additional context

[SlvrEagle23]

@FiloSpaTeam When you see that error message, where are you on the application and what are you attempting to do?

Is that error preventing anything from running?

[FiloSpaTeam]

Mmmh actually webhooks doesn't works.

https://radio.unitoo.it:8005 should work from browser?

[FiloSpaTeam]

I inspected docker logs for 20minutes and seems related to some automatic process

[dvdred]

I don't know if it is related, but i updated to the same version and now my azuracast webhook are not more auto triggered, but using the "test" button works!

[FiloSpaTeam]

Looking at docker's logs i can see that every X minutes there is a PDOException. This can be related to song change and webhook trigger.

Can be?

[TheRealMakkus]

I don't know if it is related, but i updated to the same version and now my azuracast webhook are not more auto triggered, but using the "test" button works!

Same here. :-(

[SC2Mitch]

Looking at docker's logs i can see that every X minutes there is a PDOException. This can be related to song change and webhook trigger.

Can be?

Can you provide the full PDOExeption error / logs before the error pops up?

[SlvrEagle23]

The webhook issue has been fixed as of the most recent updates to the code. Update and you should have working webhooks again.

If there's another DB error popping up, please create a new issue with the full details of that error message so we can diagnose and fix that separately.