"Allowed memory size of ... bytes exhausted" #283

Activity

1. ArturMoczulski

   self-assigned this

   on Nov 3, 2017
2. ArturMoczulski commented on Nov 3, 2017

   

   ArturMoczulski

   on Nov 3, 2017

   Contributor

   More actions

   @paulrrogers thanks for bringing this up. Can you explain more how your error reporting is too verbal? I would love to see so some examples of error reports that are just too memory intensive. Especially the ones that are causing the memory exhaustion.
3. ArturMoczulski commented on Nov 17, 2017

   

   ArturMoczulski

   on Nov 17, 2017

   Contributor

   More actions

   I'm closing this issue for now. @paulrrogers if you want us to investigate further we need your help diagnosing this
4. ArturMoczulski

   closed this as completedon Nov 17, 2017
5. plaffitt commented on Apr 30, 2019

   

   plaffitt

   on Apr 30, 2019

   More actions

   Hello, I'm currently using Rollbar-php 1.4.1, and I have this error too.
   Here is what I get on rollbar.com from my production server:

   E_ERROR: Allowed memory size of 134217728 bytes exhausted (tried to allocate 98570240 bytes): Allowed memory size of 134217728 bytes exhausted (tried to allocate 98570240 bytes) (Most recent call first)
   
   File /composer/vendor/rollbar/rollbar/src/Payload/EncodedPayload.php line 37
   

   I can help you to investigate further, what do you need to know ?
6. brianr

   reopened this on May 4, 2019
7. AronNovak commented on Mar 18, 2020

   

   AronNovak

   on Mar 18, 2020

   Contributor

   More actions

   We do have the same symptom. There's a complex flow in the Drupal application, without Rollbar, it works, with Rollbar, the memory limit is exceeded. Likely a notice or a warning is generated at some point and Rollbar doesn't have enough memory to prepare properly the payload that should be sent to the server. Checking what could be done about it.
8. j6s commented on Jul 21, 2020

   

   j6s

   on Jul 21, 2020

   More actions

   We had this problem as well. In our case it turned out that the stack traces contained UploadedFile objects which were tried to be encoded fully. Extending Rollbar\RollbarLogger and customizing getPayload to filter out / replace these objects with static strings did the trick in our case.
9. danielmorell

   added this to the v4.2.0 milestone on Jan 10, 2025
10. danielmorell

    assigned

    danielmorell

    and unassigned

    ArturMoczulski

    on Jan 10, 2025
11. danielmorell

    modified the milestones: v4.2.0, v4.3.0 on Nov 25, 2025