@hiredman, Think I found the problem (though not the solution yet). I slowly added lines to my minimal example to figure out the offending line. It turned out to be a >!
where I put the result into another channel. This other channel interacts with a library I’m using. I know the library also makes use of async processes, maybe something could be interacting there?
I thought this could be related to some known bugs, the first two results of this quick search are interesting: https://clojure.atlassian.net/browse/ASYNC-223?jql=project%20%3D%20ASYNC%20AND%20status%20%3D%20Open%20AND%20text%20~%20%22local%22%20ORDER%20BY%20priority%20DESC
Not sure these are what's at play in your case, these 2 existing issues talk about memory leaks over local bindings, meaning the symptom is an OOM error. Still, you seem to have some issue with a local binding value...
Thanks. I found those too, not sure they apply to my case. I’m planning to spent some time on the issue again today.