Skip to content

Avoid using copying property as a block value#506

Merged
jspahrsummers merged 1 commit intoReactiveCocoa:masterfrom
kkazuo:avoid-copying-block-property
May 22, 2013
Merged

Avoid using copying property as a block value#506
jspahrsummers merged 1 commit intoReactiveCocoa:masterfrom
kkazuo:avoid-copying-block-property

Conversation

@kkazuo
Copy link
Contributor

@kkazuo kkazuo commented May 22, 2013

This may fix #505 leak issue.

I'm sorry but I can not explain why this patch could fix the leak.
It is my bad know-how.

@Coneko
Copy link
Member

Coneko commented May 22, 2013

As far as I can tell by using it in a sample app, this fixes #505, so it looks ok to me.

jspahrsummers added a commit that referenced this pull request May 22, 2013
@jspahrsummers jspahrsummers merged commit 6dd8007 into ReactiveCocoa:master May 22, 2013
@jspahrsummers
Copy link
Member

This does indeed fix it. I don't understand why either.

Thanks for the fix, though! 🌟

@jspahrsummers jspahrsummers mentioned this pull request May 22, 2013
@Coneko
Copy link
Member

Coneko commented May 22, 2013

There are other uses of copy properties with block types in the framework, should we change them all or just keep this bug in mind in case something similar pops up again?

@jspahrsummers
Copy link
Member

Tentatively, I think we should just keep this in mind. I haven't seen any other leaks. Maybe there's just something weird with how we override dealloc, set the blocks from a class method, cast them, or something else.

@kkazuo kkazuo deleted the avoid-copying-block-property branch May 22, 2013 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Is this a leak?

3 participants