ppkarwasz commented on issue #3569: URL: https://github.com/apache/logging-log4j2/issues/3569#issuecomment-2754036129
> However, with the same configuration and code in version 2.23.1, why didn’t I observe this memory increase? What specific code changes from 2.23.1 to 2.24.3 might have caused this memory behavior change? Apparently the behavior in `2.23.1` was due to a bug (see #2379), which disabled part of the GC-free behavior. To draw some conclusions from this thread, what are your expectations regarding GC-free mode? - Do you expect Log4j Core to pre-allocate `StringBuilder`s of size [`log4j2.initialReusableMsgSize`](https://logging.apache.org/log4j/2.x/manual/garbagefree.html#log4j2.initialReusableMsgSize) instead of doing it on-demand? - If the `ThreadContextMap` is in GC-free mode the maps that contain context data never shrink. Should there be a configuration option to shrink them, when they are cleared? cc/@vy -- 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
