-
Notifications
You must be signed in to change notification settings - Fork 397
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.
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
group_by with not completed observable issue #403
Comments
Hard to say without specific repro, but I would assume that something has stored the |
The source is still valid in the initial variable. I will try harder to create minimal example |
Commented on_completed:
Uncommented
|
The issue is certainly in the group_by not the flat_map |
In both case at the unsubscribe, the hook (held by the lambda) should be released. Because there is no link to the observable anymore |
this is probably a bug in the lifetime - possibly introduced by (8065a79#diff-9430ecceb5eeb688548de212b7fd57be) Pure speculation, but it may be similar to the bug in I will add this to the backlog - thank you for the report! as a workaround until this bug is fixed, adding a |
I was on a old version, seems to be solved in the master |
I found an potential issue with flat_map operation when source the is a scoped observable using a factory holding a shared pointer.
In this case my shared pointer is not released after the last unsubscribe of the observable returned by flat_map.
I didn't succeed to produce a minimal example that trigger this issue, but a quick and dirty hack seems to solve the issue:
if I "reset" the state_type source (which is manly not used):
this->source = source_type();
my smart pointer is released when I unsubscribe.
Maybe this is an issue on my side, but I go many times through my code, I don't see the issue
The text was updated successfully, but these errors were encountered: