core-async

tianshu 2019-01-21T07:50:11.083200Z

@alexmiller @noisesmith @hiredman thanks for the reply, I finally found this was caused by an error raised in a go block(not thread macro). that's wired, in the thread tab I can see there're so many async-thread-macro thread didn't finish, staying in Park state.

tianshu 2019-01-21T07:52:35.083800Z

I fixed the issue by catching the exception in go block.

tianshu 2019-01-21T07:53:31.084200Z

@alexmiller my word async block means go block.