Set down MAX_NON_FREE_HAZARDS in conc::local to avoid unnecessari…

…ly high memory usage. In particular, hazards were laying around for an indefinite time, as they were never used again, yet were in a non-free state, blocking garbage collection of some garbage.
redox-os · Jul 26, 2017 · 4b8217f · 4b8217f
1 parent ab3c74d
commit 4b8217f
Showing 1 changed file with 1 addition and 1 deletion.
diff --git a/conc/src/local.rs b/conc/src/local.rs
@@ -143,7 +143,7 @@ impl State {
         ///
         /// With "cleaning up" we mean setting the state of the hazards to "free" in order to allow
         /// garbage collection of the object it is currently protecting.
-        const MAX_NON_FREE_HAZARDS: usize = 128;
+        const MAX_NON_FREE_HAZARDS: usize = 16;
 
         // Push the given hazard to the cache.
         self.available_hazards.push(hazard);