The error is caused by writing to STDOUT in a finalizer after STDOUT itself has been closed. The comment refers to removing a deprecation warning in the finalizer (the warning of course writes to STDOUT). So either you still have that problem or one of your own finalizers writes to STDOUT.
On Thursday, September 17, 2015 at 5:40:24 PM UTC+10, Andreas Lobinger wrote: > > In the issue it is mentioned, that this should go away with something in > the deprecation warning. I just got the same as above with a recent > v0.4.0-rc1 but only sometimes. Should i just post to the closed issue, or > open my own? >
