Workaround or fix

TODO

@@ -2,3 +2,4 @@ Running the server and test3_latency, and then starting and
 interrupting test1_latency repeatedly, the server eventually corrupts
 itself and will no longer let test1_latency bind and receive
 messages. Sometimes test3_latency stops too.
+  [TENTATIVE FIX: see try/with in write_sexp in relay.ml]

relay.ml

@@ -61,7 +61,7 @@ let relay_main peername cin cout =
   let mtx = Mutex.create () in
   let write_sexp s =
     Mutex.lock mtx;
-    output_sexp cout s;
+    (try output_sexp cout s with Sys_error _ -> ()); (* TODO: try removing this *)
     Mutex.unlock mtx
   in
   let flush_control = Event.new_channel () in