I was pointed to Matthias Sohn (jgit commiter) let's see if he has an idea,
before we do a release of this.
His first thought was the WindowCache.reconfigure() - but Robert already fixed
that.
/Domi
> Am 28.10.2013 um 20:51 schrieb "Robert Scholte" :
>
> @Kristian: Brilliant data!
>
> @Dennis:
@Kristian: Brilliant data!
@Dennis: the statistics have changed[1]. I managed to fix it a bit, but as
Kristian mentioned: some parts are out of reach and can't be closed by our
code (let's avoid reflection!).
I believe that in this case the Windows behavior is the preferred one: if
you op
Hi,
The vote has passed with the following result:
+1 (binding): Robert Scholte, Hervé BOUTEMY, Olivier Lamy
+1 (non binding):
I will promote the artifacts to the central repo.
Op Wed, 23 Oct 2013 21:52:48 +0200 schreef Robert Scholte
:
Hi,
We solved 3 issues:
http://jira.codehaus.org/se
I just filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=420502
The bug seems to affect "most" jgit operations and is not limited to
one single call/feature. I looked at the jgit codebase and to my
understanding the file handles in question seem to be lacking a
consistent deallocation strategy (
Thanks a lot Kristian!
Do I understand you correctly that the leak is in the jgit Checkout command?
If so, there are probably more leaks in there since 9 of our tests
fail, each testing a different command. Some tests do succeed though.
So how do we proceed with this?
Submit patches for jgit?
Rel
Finding this kind of leaks with my graciously provided OSS license of
YJP is like stealing candy from children
export MAVEN_OPTS="-Xms512m -Xmx2084m -XX:MaxPermSize=512m
-agentpath:C:/java/yjp-12.0.6/bin/win64/yjpagent.dll=onexit=snapshot"
c:/java/apache-maven-3.1.1/bin/mvn $@
Run test with forkM
