Receive doesn't work after TryReceiveAll in TPL Dataflow - by svick

Status : 


Sign in
to vote
ID 785185 Comments
Status Active Workarounds
Type Bug Repros 4
Opened 4/20/2013 3:58:36 AM
Access Restriction Public


Per, under certain circumstances, Receive() on a TPL Dataflow block will block indefinitely, even though an item is posted to the block.
Sign in to post a comment.
Posted by PeteBeech on 4/1/2014 at 8:52 AM
Just asked the team for the status on this one, and received following (posted here with their permission):

Hi Pete,
    We have reviewed some options for a fix, but the fix was rejected on grounds that it could break compat. IIRC the fix was in itself simple, but the fix was so low in the stack that we would risk breaking other scenarios.

We are keeping this active in the hope that we can take a breaking change when we update to a new baseline.


Posted by Karl He on 2/21/2014 at 12:02 AM
Hi, TPL dataflow isn't dead, is it?
Posted by svick on 12/20/2013 at 12:20 PM
It has been 10 months and there were several updates during that time (4.5.14 is the newest), but it seems this bug still wasn't fixed. Could somebody look at this again?
Posted by Karl He on 9/5/2013 at 11:26 PM
I've also met this issue. On my computer, it is OutputAvailableAsync() that blocks forever after calling TryReceiveAll(). Using TryReceive()/ReceiveAsync() instead works around the problem. So there must be some problem with TryReceiveAll(). Please fix it. Thanks.
Posted by PeteBeech on 7/15/2013 at 2:54 PM
I've just noticed a new update of TPL.Dataflow from 1/7/2013. Does this include the bugfix for this issue that you said would be in the next update?
Posted by Microsoft on 5/2/2013 at 3:33 PM
Hi svick,

Thanks for reporting the bug. We don't have a timeline for shipping an update to TPL Dataflow, but we will fix it in the next update.

Immo Landwerth
.NET Framework Team
Posted by Microsoft on 4/21/2013 at 11:55 PM
Thank you for submitting feedback on Visual Studio and .NET Framework. Your issue has been routed to the appropriate VS development team for investigation. We will contact you if we require any additional information.
Posted by Microsoft on 4/20/2013 at 4:51 AM
Thank you for your feedback, we are currently reviewing the issue you have submitted. If this issue is urgent, please contact support directly(