You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 15, 2019. It is now read-only.
Because of the "while True"-conditions in the run()-function, there is no clean exit when a python flow graph is stopped using the .stop() method. This leads to not freeing the TCP port and the remaining flow graph, especially when running a flow graph containing gr-gpredict-doppler from a python application and using the .start(), .stop() and .wait() flow graph methods.
It works in GNU Radio Companion because it kills flow graphs instead of stopping them, but this behaviour should be avoided.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Because of the "while True"-conditions in the run()-function, there is no clean exit when a python flow graph is stopped using the .stop() method. This leads to not freeing the TCP port and the remaining flow graph, especially when running a flow graph containing gr-gpredict-doppler from a python application and using the .start(), .stop() and .wait() flow graph methods.
It works in GNU Radio Companion because it kills flow graphs instead of stopping them, but this behaviour should be avoided.
The text was updated successfully, but these errors were encountered: