Skip to content

ErrorHandler produces OOM error when trying to handle a previous OOM error #40824

@rasmustnilsson

Description

@rasmustnilsson

Symfony version(s) affected: 4.4.16, 5.2.6

Description
On some OOM errors the Symfony ErrorHandler itself throws an OOM error trying to handle the previous error. This is a problem as it can make handling OOM errors impossible to handle.

This is the php output:

Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 20480 bytes) in /app/src/BugCommand.php on line 18
Fatal error: Allowed memory size of 33554432 bytes exhausted (tried to allocate 32768 bytes) in /app/vendor/symfony/error-handler/Error/OutOfMemoryError.php on line 1

The second fatal error is not expected.

How to reproduce
https://github.com/tachnik/reproduce-oom-in-error-handler-bug

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions

      pFad - Phonifier reborn

      Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

      Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


      Alternative Proxies:

      Alternative Proxy

      pFad Proxy

      pFad v3 Proxy

      pFad v4 Proxy