Fork me on GitHub

@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?


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.