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
The RxCpp operator subscribe_on is used in several of the RxROS functions/observables to run in dedicated threads. However, the subscribe_on operation spawns an unexpected number of threads. For a simple program that created an observable from a topic, performed a map operation and published it to a new topic at least 10 threads were spawned. The expected number was one.
Preliminary investigations have shown that
The problem is general and not only associated with RxROS.
The problem does not depend on the size of the program or the number of used operations.
It looks like the subscribe_on creates a pool of threads - maybe for future use.
The problem should be further investigated and maybe forwarded to the RxCpp team.
The text was updated successfully, but these errors were encountered:
The RxCpp operator subscribe_on is used in several of the RxROS functions/observables to run in dedicated threads. However, the subscribe_on operation spawns an unexpected number of threads. For a simple program that created an observable from a topic, performed a map operation and published it to a new topic at least 10 threads were spawned. The expected number was one.
Preliminary investigations have shown that
It looks like the subscribe_on creates a pool of threads - maybe for future use.
The problem should be further investigated and maybe forwarded to the RxCpp team.
The text was updated successfully, but these errors were encountered: