Bug DBSEO Causes Endless Loop in Cronjobs

[losasso]

Hello,

since when we installed DBSEO, users have not been receiving all their daily digest e-mails from vBulletin. We investigated this, and we figured out that in some days, DBSEO causes the system to go into an endless loop which uses limitless memory. This is the error we get when trying to execute the cron for daily digests manually:

Fatal error: Allowed memory size of 171966464 bytes exhausted (tried to allocate 3200119 bytes) in /vbpathhere/vb/dbtech/dbseo/includes/class_db.php on line 757

Regardless of the amount of memory we throw to the script, it allocates all of it.

Thanks.

 

[losasso]

We updated to the latest DBSEO build and the issue persists.

 

[Fillip H.]

Can you show me what's on line 757 of the relevant file for you?

Also, are you able to reproduce this issue if you go to the DBSEO CP and click to manually rebuild the sitemap?

 

[losasso]

Hello, it is caused by a regular expression:

$query = preg_replace('/\$(\w+)/', $this->config['Database']['tableprefix'] . '$1', $sql);

In the latest version this is on line 758.

The sitemap rebuilding does not have anything related to this it seems; it works fine.

This error is triggered with the daily digest cronjob.

 

[Fillip H.]

I am unable to replicate this issue by manually running that cron job. Can you please confirm whether this can be triggered on command @ your site?

 

[losasso]

Hello,

yes, it can be triggered on command. It happens everytime there are e-mails needing to be sent.

 

[Fillip H.]

Can you try turning off the "Rewrite Emails" setting in the DBSEO CP and see if that makes a difference for you?

 

[losasso]

Hello,

yes, this fixed the issue!

 

[DragonByte Technologies]

Hello losasso,

This ticket has now been closed with the status Fixed.

We hope your issue or question has been addressed to your satisfaction. If not, please feel free to re-open it by clicking this link.

If you have any further issues or questions, please feel free to start a new support ticket via the button at the top of every page.

Thank you!