[client] Memory management; handle OOM when hashing, do not skip blocks

Try to free some references regarding transfers earlier, e.g. the hash
worker and list of hashes as soon as hashing is finished on upload, not
only when the upload is finished and the window is closed.
Properly delay hashing of blocks in OOM scenarios, and be more
conservative with the number of hash workers, i.e. take maximum JVM
memory into account.
Also, improve thread naming.

1 files changed, 1 insertions, 1 deletions

diff --git a/dozentenmodul/src/main/java/org/openslx/dozmod/thrift/UploadInitiator.java b/dozentenmodul/src/main/java/org/openslx/dozmod/thrift/UploadInitiator.java
index efa65bab..811eb447 100644
--- a/dozentenmodul/src/main/java/org/openslx/dozmod/thrift/UploadInitiator.java
+++ b/dozentenmodul/src/main/java/org/openslx/dozmod/thrift/UploadInitiator.java
@@ -174,7 +174,7 @@ public class UploadInitiator {
 					return;
 				}
 				uploadTask.setMinConnections(Config.getTransferConnectionCount());
-				Thread uploadThread = new Thread(uploadTask);
+				Thread uploadThread = new Thread(uploadTask, "UploadTask");
 				uploadThread.setDaemon(true);
 				uploadThread.start();
 			}