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.

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

Fixed multiple calls to onStart. #2983

Merged
merged 1 commit into from
Jun 17, 2015
Merged

Conversation

akarnokd
Copy link
Member

Started investigating multiple calls to onStart based on #2979 and found a bunch, but since onStart can be overridden, I might have missed cases. In addition, I've found a single place where a producer is set twice on a subscriber but again, many other places may exist.

@akarnokd akarnokd added the Bug label May 26, 2015
akarnokd added a commit that referenced this pull request Jun 17, 2015
Fixed multiple calls to onStart.
@akarnokd akarnokd merged commit a40a413 into ReactiveX:1.x Jun 17, 2015
@akarnokd akarnokd deleted the MultiOnStartFix branch June 17, 2015 11:56
@ibaca
Copy link

ibaca commented Jul 7, 2015

(I know that is easy to complain 😉) This decorator strategy is not very memory friendly, you have this annoying (gwt compatibility perspective) AtomicXxxFieldUpdater in a lot of places to reduce memory usage, and you end up adding this decorators to only disable one method call.

What do you think?. Thanks to solve the problem anyway 😄.

@davidmoten
Copy link
Collaborator

Yikes! There's a lot of stuffed up backpressure fixed here. I'm hoping we can release soon.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants