Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

If an output port has no connections, block should not send messages #56

Open
jfischer opened this issue Apr 20, 2012 · 0 comments
Open

If an output port has no connections, block should not send messages #56

jfischer opened this issue Apr 20, 2012 · 0 comments
Assignees
@t-saideep

Comments

@jfischer
Copy link
Contributor

Currently, if we have an output port with no sinks, messages are send to the queue and never dequeued. In addition to the performance issue, this could cause the block to hang if the queue gets too full.

Workaround: hook empty output ports to a null block.
@ghost ghost assigned t-saideep Apr 20, 2012
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@t-saideep t-saideep

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@jfischer @t-saideep