GitHub user xnslong opened a pull request:
https://github.com/apache/logging-log4j2/pull/92
consider the StringBuilder's capacity instead of content length when do the
trim
The trim operation aims at releasing the too much memory occupied by the
`StringBuilder`. So when the StringBuilder really contains few effective
characters, but with large capacity, should also be trimmed.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/xnslong/logging-log4j2 master
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/logging-log4j2/pull/92.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #92
----
commit d61379bc66b977f53f51e0c5caeee7193aca1f32
Author: Jerry <sz...@qq.com>
Date: 2017-07-11T09:15:36Z
Merge pull request #1 from apache/master
pull latest changes from base
commit ab07e40e178e62e07234d45a056770370be7e1cc
Author: xnslong <xnsl...@outlook.com>
Date: 2017-07-11T09:40:21Z
StringBuilders determine if trim is necessary on StringBuilders capacity
instead of content length
commit 9db3f5115e2eb047562fcf4c1e34fa1d7c8e4e86
Author: xnslong <xnsl...@outlook.com>
Date: 2017-07-11T09:56:38Z
update test case
----
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
