StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
text
Body
copied!<p>It looks like your code is trying to allocate a chunk of 78MB based on the error message.</p> <p>Check your code for anything that might try and allocate a really large chunk of memory at once. This is probably not caused by a failure to release smaller objects, since the failed allocation block is large.</p> <p>If you post a snippet of code that is causing this, I would be happy to have a look and try for a more detailed reply.</p> <p>As for finding out if you sent to everyone or not, check of your email server (SMTP server) writes a log of sent messages. If so, you may be able to get a list of people who received the email. In general, I would suggest you modify your PHP code to log to a file or database each email that was sent, in case you have a crash in the future.</p> <p>EDIT after seeing code:</p> <p>On the surface, it looks like the object that represents the email and attachment is created once and re-used. </p> <p>I suggest you debug the code locally.</p> <p>First, establish a memory limit equal to what you have in production. Try <a href="http://ez.no/ezpublish/documentation/configuration/troubleshooting/not_enough_php_memory" rel="nofollow noreferrer">this resource</a> to understand how.</p> <p>Then, add some debug output inside your loop to see how much <a href="http://php.net/manual/en/function.memory-get-usage.php" rel="nofollow noreferrer">memory is available</a> after each iteration.</p> <p>Finally, run the code locally, but substitute either your email address or a known bad email address preferably at your domain (so you don't spam people). Watch memory usage as your send progresses.</p> <p>This should hopefully help you narrow down the cause of the error.</p> <p>EDIT 2:</p> <p>OK, after seeing that memory usage is continually growing, a little google magic turned up that this is a known issue with a <a href="http://framework.zend.com/issues/browse/ZF-8278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel" rel="nofollow noreferrer">reported workaround</a>.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload