Log4j 2
  1. Log4j 2
  2. LOG4J2-304

Async Loggers cause excessive memory usage and GC pauses

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: 2.0-beta9
    • Component/s: Core
    • Labels:
      None

      Description

      Log events (or log event attributes) are put in the ring buffer, but are never removed. The ring buffer keeps a reference to these objects until it wraps around and the same slot is re-used for another log event.

      This means that:

      • the memory used by the log events cannot be GC-ed until the ring buffer wraps
      • by the time the ring buffer wraps, the objects almost certainly have been promoted to the old generation, where they may cause heap fragmentation resulting in long pauses when the GC compacts the heap.

      The solution is to clear the ring buffer references immediately after the log event has been fully processed.

        Activity

        Hide
        Remko Popma added a comment -

        Fixed in revision 1502380.

        Show
        Remko Popma added a comment - Fixed in revision 1502380.

          People

          • Assignee:
            Remko Popma
            Reporter:
            Remko Popma
          • Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development