vy commented on issue #3511: URL: https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2692873251
@ByteExceptionM, thanks so much for the report. `StatusLogger` has gone through a significant overhaul since `2.22.1`, would you mind trying out the most recent version, i.e., `2.24.3`, please? If this doesn't fix your problem, would you mind providing the following details, please? 1. The Log4j configuration (e.g., `log4j2.xml`) 2. The arguments passed to the associated `java` process The size of `StatusLogger::buffer` is determined by the `log4j2.status.entries` system property. This was defaulting to 200 in `2.22.1` (hence the `200 elements` you see in the screenshot you shared) and, after the overhaul carried out in `2.23.1`, switched to 0. It is still puzzling how 200 `StatusData` instances can sum up to 4.9 GB. Nevertheless, in the worst case, you can set the `log4j2.status.entries` system property to 0 as a workaround. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: notifications-unsubscr...@logging.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
