Fix apparent off-by-one error in calculation of MAX_ALLOCATING_THREADS
authorMartin Kroeker <martin@ruby.chemie.uni-freiburg.de>
Sat, 30 Jun 2018 21:57:50 +0000 (23:57 +0200)
committerGitHub <noreply@github.com>
Sat, 30 Jun 2018 21:57:50 +0000 (23:57 +0200)
fixes #1641

driver/others/memory.c

index 7eff16c..98bcfb2 100644 (file)
@@ -497,7 +497,7 @@ static const int allocation_block_size = BUFFER_SIZE + sizeof(struct alloc_t);
 #if defined(SMP) && !defined(USE_OPENMP)
 /* This is the number of threads than can be spawned by the server, which is the
    server plus the number of threads in the thread pool */
-#  define MAX_ALLOCATING_THREADS MAX_CPU_NUMBER * 2 * MAX_PARALLEL_NUMBER
+#  define MAX_ALLOCATING_THREADS MAX_CPU_NUMBER * 2 * MAX_PARALLEL_NUMBER +1
 static int next_memory_table_pos = 0;
 #  if defined(HAS_COMPILER_TLS)
 /* Use compiler generated thread-local-storage */