ByteExceptionM commented on issue #3511:
URL:
https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2742541142
Hey! The error has not occurred since a memory leak was fixed in another
software I use. I would therefore close the issue at this point, and would
still like to thank
ByteExceptionM closed issue #3511: Possible Memory Leak in StatusLogger’s
ConcurrentLinkedQueue
URL: https://github.com/apache/logging-log4j2/issues/3511
--
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
ByteExceptionM commented on issue #3511:
URL:
https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2701264737
> > 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 Log
vy commented on issue #3511:
URL:
https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2701176267
> I applied the workaround by setting: `LOG4J_STATUS_ENTRIES=0`
@ByteExceptionM, can you explain what do you exactly mean by applying this
setting? Do you pass this as an en
ppkarwasz commented on issue #3511:
URL:
https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2700608924
> 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.
ByteExceptionM commented on issue #3511:
URL:
https://github.com/apache/logging-log4j2/issues/3511#issuecomment-2694898695
Hey, @vy!
I applied the workaround by setting: `LOG4J_STATUS_ENTRIES=0`.
At first, it seemed to work fine. The server has been running for **about 8
hours
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
**en
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.
ByteExceptionM opened a new issue, #3511:
URL: https://github.com/apache/logging-log4j2/issues/3511
## Description
Log4j2's `StatusLogger$BoundedQueue` is causing a **memory leak**, where
millions of `ConcurrentLinkedQueue$Node` instances are being retained, leading
to extreme memory
