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
Hi, I'm trying to use extended Subjects with custom teardown logic and use refCount() to close them when they are no longer in use.
These subjects are chain subscribed like
The problem I'm seeing is that if inputs change and recalculate the DataPaths needed, the DataPath observables that are no longer being used by the pipeline are not torn down. Is this an issue with the way my pipelines are designed? Do I need to include logic to explicitly close the old dataPath requests? Do I need to move the refCount further up the tree?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi, I'm trying to use extended Subjects with custom teardown logic and use refCount() to close them when they are no longer in use.
These subjects are chain subscribed like
The problem I'm seeing is that if inputs change and recalculate the DataPaths needed, the DataPath observables that are no longer being used by the pipeline are not torn down. Is this an issue with the way my pipelines are designed? Do I need to include logic to explicitly close the old dataPath requests? Do I need to move the refCount further up the tree?
Beta Was this translation helpful? Give feedback.
All reactions