ByteExceptionM commented on issue #3511: URL: https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2693672301
Hi, @vy! As you can see in the screenshots I provided, the issue isn't limited to just the **200 StatusData instances**. The memory usage is caused by an **enormous amount of `ConcurrentLinkedQueue$Node` objects**, with **hundreds of millions of entries**.  I understand that **2.23.1+ introduced major changes**, but I can't simply upgrade to **Log4j 2.24.3**, because the Minecraft server (or one of its plugins) depends on Log4j **2.22.1**. Unfortunately, I don't have a way to fully track which component is responsible for this dependency, so updating is difficult at the moment. As a workaround, I have now set the environment variable: `LOG4J_STATUS_ENTRIES=0` I will monitor whether this improves the situation. The second screenshot shows how severe the issue became yesterday, with memory usage skyrocketing to **13.9 GB due to `ConcurrentLinkedQueue$Node` instances**. I'll report back with findings after running with this new setting.  Thanks again for your help! -- 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
