CiviCRM Community Forums (archive)

Hi. I'm getting a fatal memory error when trying to access the scheduled job logs page at http://domain.com/administrator/index.php?option=com_civicrm&task=civicrm/admin/joblog&reset=1

Fatal error: Allowed memory size of 134217728 bytes exhausted (tried to allocate 80 bytes) in /srv/www/domain.org/public/administrator/components/com_civicrm/civicrm/packages/DB/mysql.php on line 383

PHP.INI has memory_limit = 128M

My understanding is that allocating more than 128MB of memory isn't wise and there is likely a memory leak somewhere in the codebase. Is this a known bug and if so is there a workaround?

Up'd the memory allocation to 256M, still errors out.

Is it possible the table being read in the log is simply too big? Is there a way to purge if so?

Where would the memory leak on the server originate? Running a stock Linode configuration, nothing crazy. Only app running on the server is CiviCRM. No performance issues are noted anywhere else except when this log is accessed.

Fatal error: Allowed memory size of 268435456 bytes exhausted (tried to allocate 74 bytes) in /srv/www/domain.com/public/administrator/components/com_civicrm/civicrm/packages/DB/mysql.php on line 383

Also tried 512...

Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 76 bytes) in /srv/www/domain.com/public/administrator/components/com_civicrm/civicrm/packages/DB/mysql.php on line 383

The table had 260,000+ records. I trimmed it to < 1000 and the script runs. There should be a check in the SQL script, or PHP somewhere. Paging perhaps.