Subgit is stuck

Hi Anton,

yes, for SVN and Git log I meant output of the log command, yet I’d also ask to add -v in the SVN log.

Hi Ildar.

The svn with a -v key contains sensitive information. Could you please tell me what exactly you need from the log? Probably, we could keep the information that you need and hide the rest that we don’t ready to show.

Hi Anton,

we need to know what exactly has been changed in every particular revision – that is, if some files were modified, or added, or a new branch created out of another branches, etc. We don’t need particular commit messages or even filenames.

Hi Ildar.

Sorry, let me clarify this. You need to know what exactly changed but you don’t need a diff?
We don’t create new branches, but I am not sure how to avoid showing you the diff, but show you the rest.
It would be helpful if you give me examples of what information are you expecting.
For example, for git, I could provide you with this:

commit e08413c66bb79e3faaee05140a78f939114f62f9
Author: Developer Name <>

xxxxxx commit message xxxxxxxx

Change-Id: Iaa09c9ea2e0b718e2a98409ae59d0eb775598fc1
Reviewed-by: Another Developer <>
Style-Verified: Jenkins Build System <>
Tests-Verified: Jenkins Build System <>

for SVN:

Hi Anton,

sorry for being not clear enough.

We definitely do not need the actual changes, only need to understand what kind of change has been made in a new revision or commit – just some files modification, or some paths copying, etc., like this for SVN:

r5794 | root | 2019-05-31 20:42:20 +0500 (Пт, 31 май 2019) | 1 line
Changed paths:
   A /pr4
   A /pr4/branches
   A /pr4/tags
   A /pr4/trunk


I’m working with Anton, and we were able to identify a few issues after performing several heap dumps. The main problem appears to be threads not terminating correctly. In the heap dump we took where subgit had exhausted its allocated 32GB of heap space, we saw 7378 threads in the waiting state . VisualVM showed them as "Piping consumer" daemon prio=5 tid=21411 TIMED_WAITING.

"Piping consumer" daemon prio=5 tid=23977 TIMED_WAITING
    at java.lang.Thread.sleep(Native Method)
       local variable:
       local variable: java.util.logging.Logger#8
       local variable: java.util.logging.Level#5
       local variable:
       local variable: java.lang.String#744171
       local variable: byte[]#124998
    at$$Lambda$<unresolved string 0x0>)

Opening the heap dump in Eclipse’s Memory Analyzer plugin totalled the occupied heap space from those threads at 28.8GB.

The stack trace of the stuck threads was identical to the problem identified in this SVNKit support topic: Replacing trilead-ssh2 with Apache sshd - #9 by joel-wenzel and I suspect that we’re seeing the same issue. If I understand the conversation in that topic, there was a fix pushed out with SVNKit 1.10.6. Our current version of Subgit (3.3.14) seems to be the latest, but it looks like it uses SVNKit 1.10.5:

[2022-06-02 10:49:42.999][subgit-install][1] SubGit version 3.3.14 ('Bobique') build #4433
[2022-06-02 10:49:43.000][subgit-install][1] System properties:             : OpenJDK Runtime Environment
sun.boot.library.path         : /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/amd64
java.vm.version               : 25.332-b09
java.vm.vendor                : Oracle Corporation
java.vendor.url               :
path.separator                : :                  : OpenJDK 64-Bit Server VM
file.encoding.pkg             :                  : US             : SUN_STANDARD
sun.os.patch.level            : unknown
jna.nosys                     : true    : Java Virtual Machine Specification
user.dir                      : <redacted>
java.runtime.version          : 1.8.0_332-8u332-ga-1~deb8u1-b09
java.awt.graphicsenv          : sun.awt.X11GraphicsEnvironment
java.endorsed.dirs            : /usr/lib/jvm/java-8-openjdk-amd64/jre/lib/endorsed
os.arch                       : amd64                : /tmp
line.separator                :

java.vm.specification.vendor  : Oracle Corporation                       : Linux
sun.jnu.encoding              : UTF-8
svnkit.http.methods           : Digest,Basic,NTLM,Negotiate
java.library.path             : /usr/java/packages/lib/amd64:/usr/lib/x86_64-linux-gnu/jni:/lib/x86_64-linux-
gnu:/usr/lib/x86_64-linux-gnu:/usr/lib/jni:/lib:/usr/lib       : Java Platform API Specification
java.class.version            : 52.0       : HotSpot 64-Bit Tiered Compilers
svnkit.ssh.client             : apache         : false
os.version                    : 4.9.0-0.bpo.6-amd64
user.home                     : <redacted>
user.timezone                 : America/Los_Angeles
java.awt.printerjob           : sun.print.PSPrinterJob
file.encoding                 : UTF-8
java.specification.version    : 1.8
java.class.path               : /usr/share/java/subgit/jansi-1.6.jar:/usr/share/java/subgit/slf4j-nop-1.7.12.

In case it’s hard to read, what I’m referring to is the /usr/share/jav a/subgit/svnkit-1.10.5-snapshot20220408143050.jar in the java.class.path

Would it be possible to get a version of Subgit with an SVNKit version bump to 1.10.6? Alternatively, is there a manual workaround that we can complete ourselves?

Thanks for the information. Indeed this problem seems to be the same as Joel Wenzel’s. As I can see from svnkit-1.10.5-snapshot20220408143050.jar filename, SVNKit version corresponds to r10827 (committed on Fri Apr 8 15:40:47 2022). But the fix to the Joel Wenzel’s problem was done at r10828. So SVNKit >=1.10.6 could be the solution. We’re planning to release a new SubGit version with the latest SVNKit (it will be 1.10.7) at the beginning of the next week.

If you don’t want, you can use the following trick:

  1. Backup


  1. Copy all JAR files from SubGit distribution’s lib/ subdirectory to


  1. Replace the SVNKit jar in

with SVNKit 1.10.6

  1. Edit

file to enumerate there all JAR files and file using <filename>=<SHA-1> format. Except the “fat jar” file (subgit-XXX_fat.jar) — delete or comment out that line. You can use the following one-liner to do that:

for file in *; do echo -n $file=; sha1sum $file | cut -f 1 -d ' '; done
  1. Delete the “fat jar” from


It’s a general trick to replace any JAR. The “fat jar” just consists of all those JARs unpacked and piled together to a single JAR file, so you can just replace it with many JAR files.

And .files file is used for consistency check: if some file’s SHA-1 doesn’t match its record in .files file, “subgit install” tries to “repair” the installation by replacing all the JARs with a “fat jar” it creates from its distribution. So it’s important to have correct SHA-1 hashes there. This list is also used to load upon start.

Anyway it would be easier just to wait for a new release, I hope it will fix the problem.

Update: SubGit 3.3.15 has been released. The problem should be fixed in that version.