Answers.Body: <p>As per @Demerit's comment, and somewhat counter-intuitively, make sure you've got your debugging settings to "off" - it's running out of memory when reporting the error. If you turn the various debugging settings off, it'll still report quite a lot of detail of the error.</p>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-10T08:51:06.613Z
Answers.Text: Many thanks Alan for your comments, and @Demerit too.
Answers.UserDisplayName: Edward Peters
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-10T08:51:55.177Z
Answers.Text: I am seeing a long [warning] as follows when a payment is created (and is not marked complete by the dummy payment processor):
Answers.UserDisplayName: Edward Peters
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-10T08:53:46.703Z
Answers.Text: Jan 10 09:49:17  [warning] Deprecated function CRM_Core_OptionGroup::getValue, use CRM_Core_PseudoConstant::getKey.
  Array
  (
      [civi.tag] => deprecated
  )
  
  Jan 10 09:49:17  [warning] Deprecated code: We have merged input params into the property bag for now but please rewrite code to not use this.
  
  Jan 10 09:49:17  [warning] Deprecated code: Unknown property 'qfKey'. We have merged this in for now as a custom property. Please rewrite your code to use PropertyBag->setCustomProperty ...
Answers.UserDisplayName: Edward Peters
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-10T08:55:09.437Z
Answers.Text: Sorry, I cannot post the whole set of warnings as there is not enough characters in this message. But there are dozens of similar lines of warning about deprecated code. I am running latest Civivcrm 5.21 on Drupal 8
Answers.UserDisplayName: Edward Peters
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-10T16:33:49.207Z
Answers.Text: Ah, cool. That new PropertyBag code just got merged recently, you might have encountered an issue with it. https://lab.civicrm.org/dev/financial/issues/82
  What payment processor are you using?
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-28T01:30:53.780Z
Answers.Text: Running into issues that have thrown errors  (ConfigAndLog) re: civi-tag deprecated and "Property bag" using Webform registrations with Stripe (D7 and Civi 5.21).   (No memory issue just failure to complete transactions under certain conditions)
Answers.UserDisplayName: Dave T
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-28T17:23:16.380Z
Answers.Text: @DaveT - you'll want to create a new post with more details if you want anyone to look at that.
Answers.UserDisplayName: Alan Dixon
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-02-28T21:58:36.550Z
Answers.Text: Thanks, will do
Answers.UserDisplayName: Dave T
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-01-07T16:21:29.093Z
Answers.LastActivityDate: 2020-01-07T16:21:29.093Z
Answers.UserDisplayName: Alan Dixon
Body: <p>I am getting reports from users of blank screens when going to register for an event. This does not happen for most users.
  The PHP error log says:</p>
  
  <p><code>PHP Fatal error:  Allowed memory size of 536870912 bytes exhausted (tried to allocate 400572416 bytes) in /home/sclgulf/public_html/sclgulf/vendor/civicrm/civicrm-core/CRM/Core/Error.php on line 520</code></p>
  
  <p>There is no error in the CiviCRM log in the ConfigAndLog directory.
  I have tried allocating 1GB instead of 512MB and it makes no difference.
  Can anyone help me debug this please?</p>
  
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-01-06T14:04:09.837Z
Comments.Text: Can you comment out the `var_dump` statement at line 520? Then it should show the actual error when it happens. I think it's running out of memory trying to dump the variable before it gets to say what the error is.
Comments.UserDisplayName: Demerit
Comments.ContentLicense: CC BY-SA 4.0
Comments.CreationDate: 2020-01-10T17:01:46.903Z
Comments.Text: Hi, "There is no error in the CiviCRM log in the ConfigAndLog directory." that seems odd - can you double-check the permissions on the directory? Also would you mind updating your question with which version of CiviCRM you're on, and which payment processors you are using [on that event]? Also whether you're using PHP FPM or Apache's mod php?
Comments.UserDisplayName: artfulrobot
Tags: <php>
Title: Exhausted memory error
ThreadText: # Exhausted memory error
  
  (Asked by: username_0 on 2020-01-06)
  
  I am getting reports from users of blank screens when going to register for an event. This does not happen for most users.
  The PHP error log says:
  
  `PHP Fatal error: Allowed memory size of 536870912 bytes exhausted (tried to allocate 400572416 bytes) in /home/sclgulf/public_html/sclgulf/vendor/civicrm/civicrm-core/CRM/Core/Error.php on line 520`
  
  There is no error in the CiviCRM log in the ConfigAndLog directory.
  I have tried allocating 1GB instead of 512MB and it makes no difference.
  Can anyone help me debug this please?
  
  **Tags:** php
  
  > **Comments:**
  > **username_1**: Can you comment out the `var_dump` statement at line 520? Then it should show the actual error when it happens. I think it's running out of memory trying to dump the variable before it gets to say what the error is.  
  > **username_2**: Hi, "There is no error in the CiviCRM log in the ConfigAndLog directory." that seems odd - can you double-check the permissions on the directory? Also would you mind updating your question with which version of CiviCRM you're on, and which payment processors you are using [on that event]? Also whether you're using PHP FPM or Apache's mod php?  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_3 on 2020-01-07. Score: 2
  
  As per @username_1's comment, and somewhat counter-intuitively, make sure you've got your debugging settings to "off" - it's running out of memory when reporting the error. If you turn the various debugging settings off, it'll still report quite a lot of detail of the error.
  
  > **Comments:**
  > **username_0**: Many thanks Alan for your comments, and @username_1 too.  
  > **username_0**: I am seeing a long [warning] as follows when a payment is created (and is not marked complete by the dummy payment processor):  
  > **username_0**: Jan 10 09:49:17  [warning] Deprecated function CRM_Core_OptionGroup::getValue, use CRM_Core_PseudoConstant::getKey. Array (     [civi.tag] => deprecated )  Jan 10 09:49:17  [warning] Deprecated code: We have merged input params into the property bag for now but please rewrite code to not use this.  Jan 10 09:49:17  [warning] Deprecated code: Unknown property 'qfKey'. We have merged this in for now as a custom property. Please rewrite your code to use PropertyBag->setCustomProperty ...  
  > **username_0**: Sorry, I cannot post the whole set of warnings as there is not enough characters in this message. But there are dozens of similar lines of warning about deprecated code. I am running latest Civivcrm 5.21 on Drupal 8  
  > **username_3**: Ah, cool. That new PropertyBag code just got merged recently, you might have encountered an issue with it. https://lab.civicrm.org/dev/financial/issues/82 What payment processor are you using?  
  > **username_4**: Running into issues that have thrown errors  (ConfigAndLog) re: civi-tag deprecated and "Property bag" using Webform registrations with Stripe (D7 and Civi 5.21).   (No memory issue just failure to complete transactions under certain conditions)  
  > **username_3**: @DaveT - you'll want to create a new post with more details if you want anyone to look at that.  
  > **username_4**: Thanks, will do  
  
  ---
  
  